I think, we need something that is doable for us in the 1/2 year timeframe. The most important project - Ansible support - may take longer, even in the Wildfly subproject, where we already did a lot. Among all that we have discussed so far, I think we can gain good progress in

a. Support Fedora Server VM as VPS using various hosting providers (e.g. Contabo, VPSserver, Amazon AWS; making contact, explore technical details, develop a provider specific variant of our Server VM, testing, deployment)

b. Fedora Server on Single Board Computer providing some Board recommendations, detailed how-to and recommendations for which tasks SBC are useful, providing a model use case, e.g server monitoring using OpenNMS or Icinga.

c. If someone of us is capable of Python, we can optimize the NFS/Samba Cockpit module and the documentation (see File sharing with NFS – Installation, and File sharing with NFS – Administration using Cockpit )

We decided on IRC meeting Wednesday, May 03, 2023:

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

c. If someone of us is capable of Python, we can optimize the NFS/Samba Cockpit module and the documentation (see File sharing with NFS – Installation, and File sharing with NFS – Administration using Cockpit )

This is still on my eventual TO-DO list, but I've been swamped with other responsibilities for the past few months.

This is still on my eventual TO-DO list, ...

That would be really great. I'm considering it it would be better to split that moduls into one for NFS and another for Samba. If I understood Alexander Bokovoy (abbra) correctly, Samba is a lot more complicated regarding the domain concept.

In the meanwhile I started a guide about installing NFS. It's still work in progress. And - shamefully - I can't get NFS to run on my test system. I'll have to do some more digging there.

Proposal of an abstract of a public presentation of Fedora Servers planning (e.g. Flock)

Fedora Server – Quo vadis

After a brief analysis of where do we currently stand, we will elaborate on the conclusions to be drawn from this and what to expect in the years ahead.

Of course, the main objective is to continue to maintain a generic server that is technology agnostic and unfettered. The outstanding feature is easy adaptability to a wide range of divers use cases, requirements and business models. So it continues to be a "multiple purpose" server.

But at the same time, technical conditions and options are changing. Given the performance increases in server hardware, many use cases and business models cannot fully utilize the hardware potential. A broad market of virtualized runtime environments has developed for this scenario (VPS/VDS). We aim to better support this target environment with additional installation media and extend the usability of Fedora.

In addition, specific usage profiles have emerged. These include, above all, use as a VM host that also provides general services natively, e.g., a database service or identity management service. Another usage profile is the HomeLab and provision of an "economical and energy-efficient home server appliance". All these are kind of „limited multiple purpose servers“. In this case, we consider to alternatively use image based installation media.