FocusGroupContainers
Launchpad Entry: NA
Created: cprofitt and duanedesign
Contributors: ubuntu beginners team council
Packages affected: NA
Summary
The current focus groups should be organized in to containers that remain stable regardless of the flux in focus groups. This change should make it easier for both other teams and ubuntu users to determine who to contact in regards to focus groups.
Release Note
Rationale
The creation of containers will aid in the following areas:
- gives other teams a contact for suggesting the need for a focus group related to their team
- allows users interested in joining the UBT to get a better idea how their focus group fits in to the Ubuntu community - contribution, support or advocacy for example
- allows for the creation of more fine grained focus groups such as packaging FG, application development FG or bug triage FG
- allows for greater scalability as the UBT grows
User stories
- Fran is a user who wants to become involved in Ubuntu and actually contribute, but is not a coder. She is not sure how to get started, but greatly wants to give back to the community. She remembers a discussion about the Ubuntu Beginners Team and finds their page. She then chooses the 'contribute' container and goes to the 'contribute' page which lists several focus groups that contribute to Ubuntu. She is excited when she sees and artwork focus group. As a high school art teacher she feels she can be successful at contributing art to the project. She decides that she wants to work with the art focus group to learn how to contribute art to Ubuntu.
- Jorge is a current Ubuntu Beginners Team member and does help desk work during the day. He wants to do a bit more than just help user on the forums, in irc channels, and on askubuntu.com. He is unsure of what other opportunities exist. He goes to the Beginners Team wiki page and clicks on the 'support' container link. When he gets to the page he sees two possible focuses - Documentation and Translation. He decides to join both focus groups so he can learn more specifics about the Ubuntu teams associated with these focus groups
- Carlos is current Ubuntu Member and one of the leaders of another Ubuntu team. His team has taken on more responsibility and he feels a need to get more people involved. His team is already over tasked so he does not feel his current members can be tasked with developing new team members. He heard about the Beginners Team at UDS-Natty and goes to the wiki page. His team contributed directly to Ubuntu so he clicks on 'contribute'. He does not see a focus group on the 'contribute' page that would link to his team so he contacts the 'container' contact and initiates a discussion about creating a new focus group in the 'contribute' area.
Assumptions
Design
You can have subsections that better describe specific parts of the issue.
Implementation
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
UI Changes
Should cover changes required to the UI, or specific UI that is required to implement this
Code Changes
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Migration
Include:
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
Test/Demo Plan
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.