Team Structure
Team structure and mission statement planning
Blueprint information
- Status:
- Complete
- Approver:
- Kaj Ailomaa
- Priority:
- Undefined
- Drafter:
- Ubuntu Studio Development
- Direction:
- Needs approval
- Assignee:
- Scott Lavender
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Started
- Milestone target:
- None
- Started by
- Kaj Ailomaa
- Completed by
- Kaj Ailomaa
Related branches
Related bugs
Sprints
Whiteboard
MISSION STATEMENT: might address the following (1):
* target audience
* typical use cases
* hardware support (can be _very_ top level at desktop/laptop to low level for particular audio interfaces)
* purposes of LTS vs non-LTS versions (i.e. non-LTS not intended for production?)
* do we support upgrade path? just LTS->LTS? (2)
(something like this? https:/
(1) even if we don't include all of this in the mission statement (which might not be a good fit), the team should probably still identify these topics and document them somewhere (website FAQ?)
(2) if we support only LTS->LTS, how do we manage backports ? Most of users will expect us to provide recent versions of our main apps (Ardour, Gimp, etc.)
Work Items
Work items:
[zequence] mission statement - create and publish one: INPROGRESS
[ubuntustudio-dev] project lead position - establish terms (LTS->LTS?) and methodology for establishing: TODO
[zequence] team positions - identify needed positions, their responsibilities, and current holders: DONE
