MentorsProposal

Differences between revisions 3 and 4
Revision 3 as of 2010-10-31 15:46:04
Size: 2217
Editor: cpe-67-242-167-198
Comment:
Revision 4 as of 2010-10-31 18:33:24
Size: 2830
Editor: cpe-67-242-167-198
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * '''Launchpad Entry''': UbuntuSpec:foo
 * '''Created''':
 * '''Contributors''':
 * '''Launchpad Entry''': [[https://blueprints.launchpad.net/ubuntu-beginners-projects/+spec/ubuntutheproject-n-beginners-team-community-onboarding|Beginners Team Onboarding]]
 * '''Created''': cprofitt and duanedesign
 * '''Contributors''': ubuntu beginners team council
Line 9: Line 9:
Mentors should be well qualified to guide ubt members in specific areas and guiding interested Ubuntu users in becoming members of teams associated with current ubt focus groups. Mentors will be approved by specific areas and can be approved in multiple areas if they desire.
Line 11: Line 12:

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.
TODO
Line 17: Line 15:
In order to integrate more efficiently with other teams mentors need to be well qualified. Well qualified will consist of a mentor being approved by a team associated with the area they wish to be approved to mentor in.
Line 19: Line 18:
 * Charles, an ubt member, wants to be an approved mentor for the QA focus group. He contacts the current lead of the QA focus group and learns the basics of assisting with QA in Ubuntu. Charles then works with a few members of the QA team he was introduced to until they are willing to recommend his becoming a mentor for ubt in the QA focus group. Once Charles gets both recommendations he is approved by ubt as a mentor for the QA focus group
 * Lisa has been involved in QA for three years and it a member of the QA team. She feels that there are not enough people involved in her team and wants to help with the on-boarding process for her team. She is directed to the ubt QA focus group and puts in an application with a reference from the QA team lead. She is approved by ubt due to this reference as a mentor for the QA focus group. She is also approved as a member of ubt.
Line 21: Line 22:

== Design ==

You can have subsections that better describe specific parts of the issue.
 * mentors will be approved on a focus group level
 * the folks currently involved in being generic 'mentors' for prospective ubt members will be approved under an 'ubt fg' or be granted a different title such as guide.
 * all current mentors will need to get recommendations to maintain mentor status
Line 27: Line 27:

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.
 * this change needs to be discussed with team leads of teams associated with current FGs and any planned FGs
 * the proposed change should be sent out to the general membership for comments and concerns
 * mentor recertification (see above assumption)
   * there will be a 1 month time period for current mentors to get recommendations for the areas they want to mentor people in
Line 45: Line 39:
== 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.
Line 52: Line 40:

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 43:

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
  • Launchpad Entry: Beginners Team Onboarding

  • Created: cprofitt and duanedesign

  • Contributors: ubuntu beginners team council

  • Packages affected:

Summary

Mentors should be well qualified to guide ubt members in specific areas and guiding interested Ubuntu users in becoming members of teams associated with current ubt focus groups. Mentors will be approved by specific areas and can be approved in multiple areas if they desire.

Release Note

TODO

Rationale

In order to integrate more efficiently with other teams mentors need to be well qualified. Well qualified will consist of a mentor being approved by a team associated with the area they wish to be approved to mentor in.

User stories

  • Charles, an ubt member, wants to be an approved mentor for the QA focus group. He contacts the current lead of the QA focus group and learns the basics of assisting with QA in Ubuntu. Charles then works with a few members of the QA team he was introduced to until they are willing to recommend his becoming a mentor for ubt in the QA focus group. Once Charles gets both recommendations he is approved by ubt as a mentor for the QA focus group
  • Lisa has been involved in QA for three years and it a member of the QA team. She feels that there are not enough people involved in her team and wants to help with the on-boarding process for her team. She is directed to the ubt QA focus group and puts in an application with a reference from the QA team lead. She is approved by ubt due to this reference as a mentor for the QA focus group. She is also approved as a member of ubt.

Assumptions

  • mentors will be approved on a focus group level
  • the folks currently involved in being generic 'mentors' for prospective ubt members will be approved under an 'ubt fg' or be granted a different title such as guide.
  • all current mentors will need to get recommendations to maintain mentor status

Implementation

  • this change needs to be discussed with team leads of teams associated with current FGs and any planned FGs
  • the proposed change should be sent out to the general membership for comments and concerns
  • mentor recertification (see above assumption)
    • there will be a 1 month time period for current mentors to get recommendations for the areas they want to mentor people in

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.

Unresolved issues

TODO

BoF agenda and discussion

TODO


CategorySpec

BeginnersTeam/Specs/NattyRoadmap/MentorsProposal (last edited 2010-11-01 15:17:57 by ip72-213-131-215)