Package Ownership
This blue print is to outline how ownership will be established within Launchpad. Because IUS packages are relatively small in numbers in comparison to a full distro it would make sense to simplify how packagers are associated with a package (maybe).
Traditional Model:
* Package has a primary owner, as well as any number of co-owners (secondary/backup)
* Pros: There is clarity in ownership. Easy to point the finger... easy to see who is/isn't carrying their weight.
* Cons: Complicated to manage via Launchpad. Would need a team for each package such as ius-php52-owners, ius-php53-owners, ius-mysql50-owners, etc.
Suggested Model:
* A package category has a team, all members equal. Kind of like a SIG.
* i.e. ius-phpdev, ius-mysqldev, ius-pythondev, ius-packagers (own all misc packages)
* Pros: Easier to manage via Launchpad. The dev group (listed above) would own all related packages (ius-phpdev owns php52, php52-pecl-X, php52-suhosin, etc). No waiting on AWOL packagers... anyone on the team can take a bug/feature request and implement it.
* Cons: No fine grain ownership or direction. Decisions would be made by a team, not by a single owner.
Blueprint information
- Status:
- Not started
- Approver:
- IUS Core Development
- Priority:
- Undefined
- Drafter:
- IUS Core Development
- Direction:
- Needs approval
- Assignee:
- IUS Core Development
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by