We need something that is doable for us in the 1/2 year timeframe.

For our most important project at the moment - Ansible support - it is quite difficult to reliably calculate the time we need to complete the work, even in the Wildfly subproject where we have already done a lot. Therefore, this project is neither really suitable for a release target nor for a release "story". We need smaller, less complex projects for this.

So far we have the following ideas to choose from:

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. 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 already on Stephen's to-do list, but probably also difficult to calculate in terms of time.

c. Backup and restore made easy, maybe based on Emmanuel's experiences with Khadas vim

d. Server Edition as identity server (typical usage configuration / setup, typical scenarios)

e. Server Edition as local or public file server (NFS, Samba, Cockpit support)

f. Server Edition as central management and installation server(pxe boot server et al.)

Some additional new options:

g. A power- and cost-efficient environment aware Home Server on Fedora Server Edition, a possible follow-up project from our (currently still unfinished) Arm project.

h. *Fedora Server live" medium, completely configured, for testing or as a rescue aid.

i. Fedora Server Edition Internet server spin completely configured Web Service server, either usable with various named server instances or as reverse proxy to containerized web service, ready to isolate logins for customers. Maybe, mail service as well.

We should choose an option that one of us is already working on or has previous experience with.

a. Would be a possibility (pboy's VM experience), but possibly more for F42 as we need to establish contacts with providers.
b. Is definitely longer term, so more likely F42.
c. Previous experience, by Emmanuel, could work for F41.
d. - f. I don't think anyone is working on this at the moment.
e. Probably not feasible for F41.
f. This could be an additional effect to our current work and should be realistic for F41
g. pboy is working on this continuously, would be feasible as a VM for F41.