operations/docs
operations/docs
3
2
Fork 11
Code Issues 3 Pull requests 3 Activity Actions

Emphasize submitting policy proposals before Change submission

Browse source
This commit is contained in:
Ben Cotton 2021-01-29 12:05:58 -05:00
commit 5a1465bb19
2 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
modules/ROOT/pages/changes_guide.adoc
View file

@ -118,6 +118,8 @@ The issue is required to be filed prior to feature submission, to ensure that so
* 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.

2
modules/ROOT/pages/changes_policy.adoc
View file

@ -76,7 +76,7 @@ System-wide changes involve system-wide defaults, critical path components, or o
For changes that require modifications to the https://docs.fedoraproject.org/en-US/packaging-guidelines/[Fedora Packaging Guidelines]:
* The person or group proposing the Change is responsible for providing a first draft of packaging guideline changes to the FPC.
* This draft does not need to be prepared prior to submitting the Change request, but must be complete by Branch point or FESCo might decide to apply the Contingency Plan.
* Ideally, this draft will be available as a pull request _before submitting the Change proposal_ so that the community and FESCo can evaluate the specific changes.
=== Release Engineering
For all system-wide changes you must file an issue in https://pagure.io/releng/issues[releng pagure] to check if your change requires Release Engineering involvement.