English
What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora Linux releases be improved?
Be sure to include the following areas if relevant:
If this is a major capability update, what has changed? For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
If this is a new functionality, what capabilities does it bring? For example: This change allows package upgrades to be performed automatically and rolled-back at will.
Does this improve some specific package or set of packages? For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
Does this improve specific Spins or Editions?
For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
Does this make the distribution more efficient? For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
Is this an improvement to maintainer processes? For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
Is this an improvement targeted as specific contributors? For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
When a Change has multiple benefits, it's better to list them all.
Scope
Proposal owners: What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?
Other developers: *REQUIRED FOR SYSTEM WIDE CHANGES* What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?
Release engineering: *REQUIRED FOR SYSTEM WIDE CHANGES* Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? Include a link to the releng issue. The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication.
Policies and guidelines: Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. Where possible, file a pull request against the appropriate policy documents _before submitting the change proposal_. That way, the community and FESCo can evaluate the specific changes required.
Trademark approval: If your Change may require trademark approval (for example, if it is a new Spin), file a https://pagure.io/Fedora-Council/tickets/issues[Fedora Council ticket] requesting trademark approval.
Alignment with Objectives: Does your proposal align with the https://docs.fedoraproject.org/en-US/project/objectives/[current Fedora Objectives]? This will not apply to many Changes, but it's important to consider when proposing a Change. Being out of alignment isn't an automatic rejection, it's just one more aspect to consider.
Upgrade/compatibility impact
*REQUIRED FOR SYSTEM WIDE CHANGES*
What happens to systems that have had a previous versions of Fedora Linux installed and are updated to the version containing this change? Will anything require manual configuration or data migration?
Will any existing functionality be no longer supported?