= System Wide Change: Add-On Modularity = https://fedoraproject.org/wiki/Changes/F28AddonModularity Change owner(s): * Stephen Gallagher <sgallagh AT redhat DOT com> * Langdon White <langdon AT redhat DOT com> == Detailed Description == Beginning in Fedora 28, Fedora will provide a new set of repositories for software and updates with alternative versions from those shipped in the default release. Please see Modularity is Dead, Long Live Modularity! [https://communityblog.fedoraproject.org/modularity-dead-long-live-modularity/] for an in-depth description of the plan. == Scope == * Proposal owners The feature owners need to provide a set of reference modules and module-streams that can be composed into the new repository. The set of available packages can and should increase over time as other packagers start taking advantage of it. * Other developers - Developers who wish to offer multiple streams of software in Fedora will need to update their packaging process to take advantage of the new dist-git branching features to allow them to build the same version across multiple releases of Fedora. - Developers who are not interested in doing this at this time will not need to make any changes. When co-maintainers of a packages have different interests, they will need to coordinate. - MirrorManager will need an update to know about the new modular repos. * Release engineering Ticket #7227 https://pagure.io/releng/issue/7227 This Change will require considerable interaction with Release Engineering and the Factory 2.0 teams. New Modular Repositories (one under release, one under updates, one under updates-testing) Stream Expansion from Factory 2.0 Automatic creation of basic modules https://pagure.io/modularity/issue/97 Default streams tagged into base Work will be tracked in Taiga — links to specific items to come. * List of deliverables Affects several release blocking deliverables. There will be an additional `fedora-repos-modular` package that will be installed by default on some Editions/Spins (each WG or SIG will need to make their own decision on whether to ship modules enabled by default). * Policies and guidelines Yes. Some guidelines are already available at https://fedoraproject.org/wiki/Module:Guidelines, however we have plans in place to vastly simplify the process, which should make packagers' lives much easier. * 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
