From Fedora Project Wiki
< SIGs
No edit summary |
|||
Line 35: | Line 35: | ||
* Should we require (or perhaps strongly suggest) koji scratch builds to be provided with the initial submission? An significant percentage of the packages I look at simply don't build. [[User:Tibbs|Tibbs]] 17:05, 20 August 2008 (UTC) | * Should we require (or perhaps strongly suggest) koji scratch builds to be provided with the initial submission? An significant percentage of the packages I look at simply don't build. [[User:Tibbs|Tibbs]] 17:05, 20 August 2008 (UTC) | ||
** Generally | ** Generally recommended IMO. Usually I reject review requests with srpms which don't build on koji with the comment "this doesn't build". However the problem is that this cannot be applied for requests by new contributors seeking for sponsors (currently I give priority over reviewing NEEDSPONSOR blockers). [[User:Mtasaka|Mamoru]] 17:30 2008-08-20 |
Revision as of 17:35, 20 August 2008
(Need a fancy header)
Fedora Package Review SIG
Who Are We?
Package Review Tickets | |
---|---|
New Review Tickets | In-progress Review Tickets |
This SIG is currently in its infancy and things are still being organized.
- Our job is to process new package review submissions and review them for quality and adherence to the Packaging Guidelines. As this is the initial experience for many new contributors to the Fedora Project, we also work towards making this procedure as enjoyable as possible.
(Need a help wanted/qualifications page that doesn't scare off too many contributors.)
Getting Involved
(Need some more structure before we can do much more.)
Scope of Action
- Actually reviewing packages.
- Coordinating reviews of difficult or large packages that may be too much for one person.
- Review triage (ensuring the form of the submission is correct, making sure the package builds and providing rpmlint output).
- Assisting new contributors in doing pre-reviews.
- Investigating modifications to the review process and initial review submission requirements.
- Generating reports and reporting to upstream committees.
Brainstorming
Since we're not yet organized, a communal brain dump can help get us started.
- Should we require (or perhaps strongly suggest) koji scratch builds to be provided with the initial submission? An significant percentage of the packages I look at simply don't build. Tibbs 17:05, 20 August 2008 (UTC)
- Generally recommended IMO. Usually I reject review requests with srpms which don't build on koji with the comment "this doesn't build". However the problem is that this cannot be applied for requests by new contributors seeking for sponsors (currently I give priority over reviewing NEEDSPONSOR blockers). Mamoru 17:30 2008-08-20