Policy for Modules in Fedora and Fedora ELN - Fedora 33 Self-Contained Change proposal

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/ModularPolicy

== Summary ==
Establish a set of rules for Modular content in Fedora to ensure an
optimal user and packager experience.

== Owner ==
* Name: [[User:Sgallagh| Stephen Gallagher]]
* Email: sgallagh(a)redhat.com

== Detailed Description ==
Over the last several months, members of the Modularity WG and FESCo
have been working to establish a policy for module inclusion in
Fedora. We now have a proposal that FESCo requested be taken to the
Fedora community via the Change Proposal.

There is a preview of the new policy available at
https://sgallagh.fedorapeople.org/docs/modularity/modularity/policies/


== Benefit to Fedora ==
This policy makes explicit what packagers can and cannot do with
Modules in Fedora, which should avoid future issues like those that
were seen during the Fedora 31 and Fedora 32 cycles.

== Scope ==
* Proposal owners:
The proposal is written, so minimal work remains. We may need to make
revisions or clarifications based on public feedback.

* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A
N/A (not a System Wide Change)

== How To Test ==
N/A (not a System Wide Change)

== User Experience ==
N/A this is not a user-facing change.

== Dependencies ==
N/A (not a System Wide Change)

== Contingency Plan ==
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)

== Documentation ==
N/A (not a System Wide Change)


-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis