Workflow for New Packages
Following on discussions the past few months on ubuntu-devel, review the current workflow for accepting new packages into Ubuntu, with an eye to refinements or improvements we could make this cycle. Includes submission to Debian, Backports, REVU (and potential for switching to DebExpo), and ARB.
Blueprint information
- Status:
- Not started
- Approver:
- Kate Stewart
- Priority:
- Undefined
- Drafter:
- Iain Lane
- Direction:
- Needs approval
- Assignee:
- Allison Randal
- Definition:
- New
- Series goal:
- Accepted for precise
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Workitems:
[mvo] Develop reports on badly reviewed and unreviewed packages: TODO
[allison] Propose closing REVU to ubuntu-devel: DONE
[allison] Propose replacing REVU with mentors.d.n, IRC, etc. to ubuntu-devel: POSTPONED
[allison] Spec requirements capabilities needed by mentors.debian.net to review Ubuntu packages: POSTPONED
[ajmitch] Write text on REVU to redirect people to the appropriate place.: DONE
[lfaraone] Kick off discussion on ubuntu-devel about what is and isn't in scope for a new package in Universe: TODO
[jonathan] Develop criteria and procedures for orphaned packages: TODO
[stefanor] Also develop criteria and procedures for orphaned packages: TODO
[jml] Develop documentation on Ubuntu maintainership from upstream perspective: TODO
[laney] Find/update/create documentation on "Why Debian?" from perspective of Ubuntu developers: TODO
- how can we make sure the flow is working correctly (social, mainly)
- what would debexpo need to gain to make a switch possible? (technical)
- welcoming new developers, starting them on the path towards deeper contributions (possibly leading to MOTU, DD, etc)
