Changes between Version 3 and Version 4 of ParrotTeams

Show
Ignore:
Timestamp:
10/17/10 06:01:43 (11 years ago)
Author:
cotto
Comment:

rework, remove redundancies, general cleanup

Legend:

Unmodified
Added
Removed
Modified
  • ParrotTeams

    v3 v4  
     1Note: This is a proposed restructuring of Parrot's developer community, not a reflection of its current state.  This proposed structure is still in flux and we are actively soliciting feedback.  If you have feedback, please reply to the thread on the parrot-dev mailing list or pose your question during the next #parrotsketch meeting, 
     2 
     3 
    14= How teams work = 
    25 
    3 == Participation == 
    4 Each team will have one person who has primary responsibility for that team.  Any interested people are strongly encouraged to participate in any team, but the team lead will have final say over membership.  Developers in a team other than the lead are referred to as team members.  A team consisting of a single member is fine, but we love having high bus numbers. 
     6== Team Structure == 
     7Each team consists of a team lead and zero or more members, all of whom are focused on a single aspect of Parrot and its community.  These areas of focus are listed below under "Teams and Responsibilities".  Developers are strongly encouraged to join teams that match their interests and skills.  Membership in a team is not a prerequisite for contributing to Parrot.   
    58 
    6 == Team Leads == 
    7 A team must consist of at least one member, who is the team lead.  Team leads are required to commit to performing their duties for a period of 6 months at a time, with a brief review and request for renewal being performed at the #parrotsketch meeting before the x.0 and x.6 releases. 
     9Teams consisting of a single member may exist, but we believe that teams of 2-4 will generally be more robust and reliable. 
    810 
    911== Qualifications == 
    10 Team membership is a formalization of a developer's prior actions.  A developer wants to join a team, the procedure is to talk to the team lead and start contributing to that team's goals.  Once a developer proves capable of working with the team and the community, the team lead will add that developer to that team.  Team membership is documented on the wiki on TeamMemberships (TODO). 
     12Team leads are required to commit to performing their duties for a period of 6 months.  A brief review and request for renewal will be presented at the first #parrotsketch meeting after the x.0.0 and x.6.0 releases.  When a team lead wishes to step down, he may select a new lead through whatever method he feels is most fitting.  The requirements for team membership are left to the discretion of the team leads. 
    1113 
    12 == Disqualification == 
    13 Maintaining team membership and team membership documentation the responsibility of the team lead.  A team lead may be ejected by a unanimous vote of the Parrot Foundation board of directors.  The reason for ejection is at the discretion of the board of directors, but the primary criteria is that the lead is unable or unwilling to carry out the team's responsibilities. 
     14Team membership is a formalization of a developer's prior actions.  If a developer wants to join a team, he should talk to the team lead and start contributing to that team's goals.  A track record of contributions toward a team's goals is generally the best way to convince a team lead to allow a developer to join.  A list of team leads and members is documented on [wiki:ParrotTeamMembers] (TODO). 
     15 
     16== Dissolution == 
     17Maintaining a functional team is the responsibility of the team lead.  In the rare case that a team ceases to function effectively or becomes unresponsive, that team may be dissolved and re-formed by a unanimous vote of the other team leads.  The precise reasons for dissolution are left to the discretion of the team leads but the primary criteria is that the lead is unable or unwilling to carry out his responsibilities.  We expect this to be extremely uncommon. 
    1418 
    1519 
     
    1721 
    1822== Architecture == 
    19 This team is responsible for the overall vision and direction of Parrot.  Their job is to determine where Parrot needs to go, keeping an eye toward the future.  They have the final say in disagreements between the Project Management Team and the Product Management Team. 
     23This team is responsible for the overall vision and direction of Parrot.  Their job is to determine where Parrot needs to go, keeping an eye toward the future.  They have the final say in conflicts between the Project Management Team and the Product Management Team, should they arise. 
    2024 
    2125== Project Management == 
     
    2327 
    2428== Community Management == 
    25 This team acts as the face of Parrot to other communities.  They are responsible for attracting new developers to Parrot, directing interested developers toward places where their interests and skills can be put to effective use.  They also serve as and advocate for current Parrot developers. 
     29This team acts as the face of Parrot to other communities.  They are responsible for attracting new developers to Parrot and directing interested developers toward places where their interests and skills can be put to effective use.  They also serve as an advocate for current Parrot developers. 
    2630 
    2731== Product Management == 
    28 This team is responsible for the vision of Parrot as a user-facing product.  They also act as an advocate for the needs of Parrot's users (e.g. HLLs and libraries such as Rakudo and Kakapo), and as an interface between Parrot and its users. 
     32This team is responsible for the vision of Parrot as a user-facing product.  They also act as an advocate for the needs of Parrot's users (e.g. HLLs and libraries such as Rakudo and Kakapo) and as an intermediary between Parrot and its users. 
    2933 
    30 == QA Management == 
    31 This team is responsible for ensuring that we have good documentation and test coverage, that existing tests are run regularly and that tests are added for new features and bug fixes.  This team may not be distinct from Project Management, but it is a distinct and vital responsibility. 
     34== Quality Assurance == 
     35This team is responsible for ensuring that Parrot has good, current documentation and a high degree of test coverage on a ma, that existing tests are run regularly on a maximal number of platforms and that tests are added for new features and bug fixes.  This team may not be distinct from Project Management, but it is a distinct and vital responsibility.