Revision of Server SBC documentation #168

Open
opened 2025-09-09 12:28:38 +00:00 by pboy · 2 comments
Owner

Goals:

  • clearly separate the „real“ Server for professional use from the SBC „special case“
  • focus on more powerful models which also run with a EDK2 firmware (or alike) module
  • Introduction of a catalog of criteria for selecting a suitable model
  • Introduction of 1-3 reference models that, based on our experience, work well and are recommended.
Goals: * clearly separate the „real“ Server for professional use from the SBC „special case“ * focus on more powerful models which also run with a EDK2 firmware (or alike) module * Introduction of a catalog of criteria for selecting a suitable model * Introduction of 1-3 reference models that, based on our experience, work well and are recommended.
Author
Owner

Metadata Update from @pboy:

  • Issue tagged with: meeting
**Metadata Update from @pboy**: - Issue tagged with: meeting
Author
Owner

Proposal for a first step:

  1. Make the current title "Special: Single Board Computers" a subdirectory
  2. Make the the current documedn "Fedora Server on Single Board Computers - Raspberry Pi & Co" the index.adoc in that subdire3ctory
  3. Move the document "ARM Single Board Computer Installation" from the "Installation" subdirectory into the new subdirectory

That way we can make a step forward into out new structure for SBC documentation with a minimum of work.

In a second step we con further improve those documents.

Proposal for a first step: 1. Make the current title "Special: Single Board Computers" a subdirectory 2. Make the the current documedn "Fedora Server on Single Board Computers - Raspberry Pi & Co" the index.adoc in that subdire3ctory 3. Move the document "ARM Single Board Computer Installation" from the "Installation" subdirectory into the new subdirectory That way we can make a step forward into out new structure for SBC documentation with a minimum of work. In a second step we con further improve those documents.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
server/tickets#168
No description provided.