From Fedora Project Wiki
(Add noinclude section) |
(Redirect Package Maintainer wiki links to docs.fp.o) |
||
| Line 1: | Line 1: | ||
{{Summer of Code Idea|Automate Packaging Review Guidelines|IDEA|jlaska|jlaska|basic python and bash programming, rpm | {{Summer of Code Idea|Automate Packaging Review Guidelines|IDEA|jlaska|jlaska|basic python and bash programming, rpm | ||
| Including new software in Fedora involves a [ | | Including new software in Fedora involves a [https://docs.fedoraproject.org/en-US/package-maintainers/Package_Review_Process/ submission process] to assess how well the software is packaged according to the [[Packaging:Guidelines|packaging guidelines]]. The packaging guidelines are exhaustive, and it's far too much for a reviewer to remember each and every step. Especially a new fedora package contributor. Many of the review steps are items for which a script or automated test could be performed by the packager (or package reviewer). It seems like it would be beneficial to provide a more consistent package review experience by automating many steps of the package review process, and possibly adjust the workflow to support packagers self-reviewing their packages using the script. | ||
}} | }} | ||
<noinclude> | <noinclude> | ||
<!-- INCLUDE DETAILS HERE --> | <!-- INCLUDE DETAILS HERE --> | ||
</noinclude> | </noinclude> | ||
Latest revision as of 11:19, 9 October 2021
Automate Packaging Review Guidelines
| Status | Contact | Mentor | Skills |
|---|---|---|---|
| IDEA | jlaska | jlaska | basic python and bash programming, rpm |
| Description | |||
| Including new software in Fedora involves a submission process to assess how well the software is packaged according to the packaging guidelines. The packaging guidelines are exhaustive, and it's far too much for a reviewer to remember each and every step. Especially a new fedora package contributor. Many of the review steps are items for which a script or automated test could be performed by the packager (or package reviewer). It seems like it would be beneficial to provide a more consistent package review experience by automating many steps of the package review process, and possibly adjust the workflow to support packagers self-reviewing their packages using the script. | |||