From Fedora Project Wiki
(Initial idea) |
(Add noinclude section) |
||
Line 2: | Line 2: | ||
| Including new software in Fedora involves a [[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. | | Including new software in Fedora involves a [[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> | |||
<!-- INCLUDE DETAILS HERE --> | |||
</noinclude> |
Revision as of 19:33, 23 April 2010
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. |