Meeting Minutes 2023

AS it looks at the moment the committee has accepted and is planning with a presentation: Fedora Server Edition – Quo Vadis? Unfortunately a workshop about Server in virtual environment, that I proposed, too, didn’t make it.

Agreed WG agrees about to use automated testing using Samba AD as the server end (instead of a native Windows server) and to keep the status of release criteria.

Full compatibility with Windows Server remains the goal regardless of the testing procedure. And an inability to connect to a real Microsoft AD server remains a release blocking criterion, since that is (and remains) the most prominent domain controller in the world.

We’ll complete the current device documentation draft with the devices nominated until now.

We want to replace the "DVD" in the naming of the installation media by "STD".

pboy has submitted a talk and a workshop idea to Flock

W’ll compose a devices list.

ACTION eseyman to post his ARM SBC list to the list by next week.

This year’s Flock will be in-person Aug. 2-4 in Cork, Ireland. We’ll discuss our contribution on mailing list and next meeting.

AGREED: The WG agrees on part 1 of the plan in issue 108 and will create a reference list.

W’ll start a list of desirable or available devices in a comment to on tracking issue #108.

W’ll consider the Phoronix list of tests for comparison.

We postpone working on it until July, when jwhimpel has time again.

AGREED: WG will perform the community survey as proposed in #110 .

AGREED: WG will pursue 'Fedora Server Edition on SBC' as first priority for F39, and 'Fedora Server Edition in virtualized environments' as 2nd priority.

AGREED: WG will pursue 'Fedora Server Edition on SBC' as the 'story' for F39 with first priority, 'Fedora Server Edition in Virtuialized environments' with 2nd priority.

ACTION: pboy will post a first draft regarding 'Fedora Server Edition on SBCs' on hackmd.io for further discussion.

On mailing list we have a first info and a draft collection of ideas. The challenge is not so much the "story" part, but the "every release" part.

ACTION: eseyman will try and think up something for next meeting

AGREED: We evaluate 2 options for F39: ServerVM support for various hosting services and Usage of SBC as a Server device

We are fine with F38 and should not experience any surprises.

Nirik created a PR as decided. It is pushed to stable and will be included in the installation media.

AGREED: Server WG would like to get a "Documentation" button/link between Download and Community in the hero graphic

AGREED: Server WG is content with the feature list and descriptions.

We will start thinking about how we’re going to get these ansible roles/playbooks into our users' hands.

AGREED: to take the same route as CoreOS and keep the old default value. (+3, 0, -2 )

ACTION: pboy will write a info about how to configure the timeout value and nirik will review

We are still missing a documentation button and link. The feature list needs some improvement.

We are still evaluating the possible impact and current configuration of the core services.

We want to add to our documentation how to make changes to the .service file if someone has an issue.

action pboy will create a summary of our discussion about service specific timeouts.

action pboy will open a mailing list discussion about interdependencies between services and the consequences.

We have still 2 unresolved issues:

action jdubby will update his Ansible/Wildfly repo

action eseyman will look at the updated repo

action pboy will provide a public server where we can work in a cooperative work on all the details

We are generally very content with the current state of the completed draft. Mowest informed that the design group considers it "near final". Anyway we can request changes after the F38 rollout.

Mowest informs about the availability of a first complete draft, although still with some placeholders. The discussion about further development is still ongoing. The current topic is the design of the header. We agree that it should express as well as possible the universality and wide scope of Fedora Server Edition (from SBC to SME to Data Center).

Next step is the finetuning of the mission statements.

We are still evaluating the possible impact and current configuration of the core services.

Mowest made contact with the revamp team. We are now in the flow to work on it. See the current mockup! The texts are a first draft. The graphical assets are mostly placeholders.

You can also follow the ongoing conversation about the current status of the website design. To give feedback, please use our pagure issue #66!

Next actions:

We will first review the Core Services of our current "Technical Specification" to see what configuration is implemented for a shutdown. Furthermore, we will consider conducting a test tag on this point, although implementation is likely to be difficult. Depending on the findings, we will decide on the further handling of the magnitude of the default timeout.

We found contradictions resp. ambiguities about the exact configuration of the current timeout configuration in Server. Nirik will clarify this.

Actions

Mowest made contact with the revamp team and introduced himself as Server contact. We are now in the flow to work on it.

The next step is to collect content for our pages. Mowest asks to contribute key ideas, messages, mission statements for the content of the page. We prefer professional, meaningful texts, not rather content-less marketing phrases, which can be found partly on some newly designed pages.

Actions