= Proposed System Wide Change: Modular Server = https://fedoraproject.org/wiki/Changes/Modular_Server Change owner(s): * Langdon White <langdon AT fedoraproject DOT org> The Modularity Working Group, Factory 2.0, Base Runtime, and Server Working Group would like to propose using the modular infrastructure for creating and delivering the Fedora Server Edition for Fedora 27. While we are still working through some of the kinks leading up to the release of Fedora 26, we believe that the changes to the infrastructure and technology implementations will be available with sufficient time to harden the components in time for the 27 release. == Detailed Description == The modularity effort is fairly well known and significantly more information may be found on the Modularity Website [ https://docs.pagure.org/modularity/ ] or the YouTube Channel [ https://www.youtube.com/channel/UC4O8G9SZwqtkIAuKcT8-JpQ ]. In short, modularity is attempting to disconnect the lifecycle of applications from 1) each other 2) the operating system while still maintaining the ease of use of a typical Linux Distro. This change proposal is to promote the work done in the Boltron Release (preview container image in advance of the F26 release) to Fedora mainline through the Fedora Server Edition. We will also be working with the community to complete the available content for Fedora Server Edition as modules. Other edition and spins will not change at this point; users who want to create a Fedora server (as opposed to capital-S Fedora Server) without Modularity can use one of these other spins, including the Fedora Cloud Base image, or else use the "everything netinst". == Scope == * Proposal owners: The Modularity WG, Factory 2.0, Base Runtime, and Server WG teams all have contributions to this effort. The work that each team is doing is significant and wide ranging. We are hoping to: - collect and incorporate feedback in to the system management experience of using modules (through dnf) - modularize a significant amount of the content available for Fedora Server (focusing on current Server roles) - define tools and best practices for implementing modules and keeping them up to date * Other developers: - Packagers are already working on modularizing applications; - the Modularity WG will provide like to support additional package maintainers in modularizing their applications * Release engineering: See [[Changes/ModularRelease]] [ https://fedoraproject.org/wiki/Changes/ModularRelease ] [ https://pagure.io/releng/issue/6852 ] * List of deliverables: This change replaces the Fedora 26 Server release-blocking deliverables with exactly the same things (DVDs and netinst images) but delivered via Modularity instead of the traditional process. Although we want to enable changes to module lifecycles over time, it is worth noting that this Change Proposal does NOT change the normal 13 month commitment for anything in the release. * Policies and guidelines: New guidelines are required, they are currently in Draft state and we will be collecting feedback to them during the F26 lifecycle for ratification prior to F27. - Fedora_Packaging_Guidelines_for_Modules [ https://fedoraproject.org/wiki/Fedora_Packaging_Guidelines_for_Modules ] - Container:Guidelines [ https://fedoraproject.org/wiki/Container:Guidelines ] At this point there are no changes expected to existing guidelines * Trademark approval: N/A (not needed for this Change) -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
