MembershipProposal
Differences between revisions 4 and 5
|
Size: 2202
Comment:
|
Size: 2250
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 19: | Line 19: |
| Jayne wants to help other users, but they are not sure how to go about it. They have a good grasp of how to troubleshoot Ubuntu issues with hardware and software configurations. | |
| Line 21: | Line 22: |
== Design == You can have subsections that better describe specific parts of the issue. |
* not all ubt members will be mentors * ubt members will show a good understanding of general Ubuntu knowledge and troubleshooting * ubt members will all be considered part of the 'support container' * ubt members may choose to focus on focus groups in other containers as well |
| Line 27: | Line 28: |
| Currently the ubt requires prospective members to choose an area to focus on, this will now become a container to focus on with a possible future focus on one or more focus groups. The membership process will follow the flow listed below: | |
| Line 28: | Line 30: |
| This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: | 1. prospective member 1. introduce yourself to the team and indicate your interest in helping Ubuntu users 1. apply for a membership vote 1. link to examples of your answering user questions if forums or askubuntu.com related 1. have references given if your answers are irc based (irc logs could also be referenced) 1. approved or re-apply after building more history 1. member wishing to join a focus group 1. contact the FG lead and express an interest in that area 1. work with the FG lead to work on a plan of action to gain the necessary knowledge |
| Line 30: | Line 40: |
| === 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. |
|
| Line 39: | Line 42: |
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. |
* all current prospects will have to be given a set of dates when the new process will be put in place * email to entire ubt team will need to be sent so they know the new process * ubt wiki pages edited to detail the new process |
| Line 52: | Line 47: |
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. |
TODO |
| Line 56: | Line 50: |
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. |
TODO |
| Line 61: | Line 54: |
---- CategorySpec |
Launchpad Entry: NA
Created: cprofitt and duanedesign
Contributors: ubuntu beginners team council
Packages affected: NA
Summary
The beginners team needs to solidify the process of becoming a member as well as defining what a member is versus what a mentor is.
Release Note
TODO
Rationale
Creating a clear process for becoming a member as well as defining what a member's role is will help the ubt scale as it grows.
User stories
Jayne wants to help other users, but they are not sure how to go about it. They have a good grasp of how to troubleshoot Ubuntu issues with hardware and software configurations.
Assumptions
- not all ubt members will be mentors
- ubt members will show a good understanding of general Ubuntu knowledge and troubleshooting
- ubt members will all be considered part of the 'support container'
- ubt members may choose to focus on focus groups in other containers as well
Implementation
Currently the ubt requires prospective members to choose an area to focus on, this will now become a container to focus on with a possible future focus on one or more focus groups. The membership process will follow the flow listed below:
- prospective member
- introduce yourself to the team and indicate your interest in helping Ubuntu users
- apply for a membership vote
- link to examples of your answering user questions if forums or askubuntu.com related
- have references given if your answers are irc based (irc logs could also be referenced)
- approved or re-apply after building more history
- member wishing to join a focus group
- contact the FG lead and express an interest in that area
- work with the FG lead to work on a plan of action to gain the necessary knowledge
Migration
- all current prospects will have to be given a set of dates when the new process will be put in place
- email to entire ubt team will need to be sent so they know the new process
- ubt wiki pages edited to detail the new process
Unresolved issues
TODO
BoF agenda and discussion
TODO
BeginnersTeam/Specs/NattyRoadmap/MembershipProposal (last edited 2010-11-02 01:28:35 by cpe-67-242-167-198)