There is a thread on devel list
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
about the future of Fedora Server. A number of people said that it's
important to them and they'd like to help keep working on it. In order for
Fedora Server to remain as an Edition, we need a regularly-meeting,
cross-functional group (packaging, documentation, testing, marketing).
This thread is for organizing that group. I'll be happy to take part in some
kick-off efforts myself, because as a former sysadmin Fedora Server is
important to me, because as Fedora Project Leader I think it has something
valuable to provide to the project, and because as a Red Hatter I think a
strong Fedora Server yields a better RHEL.
Basic needs are:
* regular meetings to make sure the ticket queue at
https://pagure.io/fedora-server/issues is kept up with
* regular updates to the Edition status dashboard
https://docs.fedoraproject.org/en-US/project/dashboard/
* update the PRD and other working documents at
https://fedoraproject.org/wiki/Server
* help with QA every release cycle
* updated marketing materials for https://getfedora.org and for press
releases every release cycle
* marketing materials for Ambassadors
* talks for sysadmin/ops-focused conferences about Fedora Server use cases
* merge Fedora Cloud Base into the edition (I can talk more about specifics
here)
* updated docs and howtos
* better connections with the System Roles project — Fedora Server is the
natural upstream home for this
* better connections with CentOS Stream
* probably more
Let's schedule a meeting for anyone interested. We can make this an
IRC meeting, or a video call, or both.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
Sooorry to write such a long Text! Please be patient.
After studying the currently available documentation I would like to open a specific thread strictly dedicated to discuss and determine what we would like to achieve regarding fedora server documentation. At the end there should be a kind of table of contents and an agreement where parts of the desired content should be placed. In a next step, existing content would then be assigned to the topics or new material would be collected.
Right from the start, we have to consider how this fits into the Fedora project as a whole, which makes it - considering the current state of affairs - a bit more complicated.
To begin with:
Matthew wrote:
> We also have
> https://docs.fedoraproject.org/en-US/fedora/rawhide/system-administrators-g…,
> which could use a _serious_ update across the board.
which might be a bit of understatement.
The problem - in my humble opinion - is not so much the existing content (the individual contributions for themselves are mostly OK, some need smaller updates), but rather the missing bits and even more the structure of the existing document body as well as missing and unclear intention, the „mission“ of the parts in their context. I have the impression the guide had been conceptualised at a time when Fedora was a uniform distribution and not differentiated into editions.
The same seems to be true for the Installation Guide above the System Administration Guide on the same page.
As a first item we need a section „Installing Fedora Server“. It should explain the various installation options and possible criteria / reasons to decide what to choose. It should explain basic decision at installation time (i.e. in Anaconda) and their effects on subsequent operation and similar content.
A „natural“ place would be the Installation Guide, but that would affect the whole text. A possible new structure could be:
- Preface, Intro, Download - just as currently
- Starting Anaconda (Cross-edition items such as keyboard, source, language, etc.)
- Installing Fedora Workstation, renamed from Installing Fedora (current text might be taken over unchanged)
- Installing Fedora Server, completely new, our part, see above
- wished for: Installing IoT. (would be nice to have an installation guide for each edition)
- Advanced Installation Options (optimal with some adjustments in relation to the editions or also unchanged)
- Technical Appendixes (unchanged)
I suppose, the System Administration Guide needs a new structure as well, eg.
- Preface, OK
- Fedora Workstation Administration (basically the current „Basic System Config)
- Fedora Server Administration (completely new, post-anaconda stuff e.g. Working with the terminal, working with Cockpit, hardening and security, and general administration tasks, e.g. organising data storage, application installation concepts, etc)
- Fedora Administration Reference (miscellaneous, cross edition focus, maybe its own guide/manual)
--- Service and Daemons
—-- OpenSSH
—-- TigerVNC
—-- DNF
—-- RPM
—-- Monitoring & Automation
—-- Wayland Display Server
And last not least we need a place for various server topics and services (web, mail, file, …), howto’s, troubleshooting instructions, etc.
Currently I see two options here:
- a dedicated box „Fedora Server“ on the docs.fedoraproject.org landing page
- or a section in Quick Docs, which, however, would escape the systematics of those pages.
So far my thoughts and suggestions. Criticism and alternatives very much appreciated.
