-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello, Server SIG!
* Server Edition should focus on slimming down such that the Fedora Cloud image
can be Server Edition instead of the custom minimal image it is today.
Open Question: should Server own and become the base container image as well?
I think that a base container could be considered the smallest example of a server and so
would fall under something the group could work on (since one of the things people are
always either focused on are "Why aren't you shipping everything" and
"Why aren't you installing nothing more than the kernel and maybe busybox?"
* We have basically given up on the original design of Server Roles,
but we
see value in Cockpit's new Server Apps[1]. We should contribute here.
* In general, the consensus was that there are two places in Server Edition
that we should focus new features around Cockpit and Ansible. Anything we want
to declare a "Server Feature" should integrate with one or both of these. We
also would like to see Cockpit provide an Ansible-based "desired state
configuration" feature that would produce an Ansible playbook that would
replicate the current state of the system for any part of it that Cockpit
understands. (I will be writing up an RFE for Cockpit shortly).
* Considering the large overlap in utility, we should probably consider closer
ties with the EPEL project.
If containers become more of a thing for EL-8 and other places, it would be useful to have
latest Fedora releases able to slot in easily. It would also be useful for the experience
server has with modules for getting that working in EPEL also.
> [1]
https://github.com/cockpit-project/cockpit/wiki/Server-Applications