< Changes
| Line 55: | Line 55: | ||
== Feedback == | == Feedback == | ||
A lot of discussion happened in the pull request: https://pagure.io/fedora-docs/modularity/pull-request/83 | |||
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --> | <!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --> | ||
Revision as of 16:02, 5 August 2020
Policy for Modules in Fedora and Fedora ELN
Summary
Establish a set of rules for Modular content in Fedora to ensure an optimal user and packager experience. At present, these rules will apply only to Fedora ELN, but are written in such a way as to be reusable for Fedora and EPEL in the future through another Change Proposal.
Owner
- Name: Stephen Gallagher
- Email: sgallagh@redhat.com <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
Current status
- Targeted release: Fedora 33
- Last updated: 2020-08-05
- FESCo issue: #2452
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
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/
Feedback
A lot of discussion happened in the pull request: https://pagure.io/fedora-docs/modularity/pull-request/83
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
- Policies and guidelines: This Change is all about documentation. See above.
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
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), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)