[svn:parrot] r37106 - trunk/docs/project

allison at svn.parrot.org allison at svn.parrot.org
Wed Mar 4 06:31:41 UTC 2009


Author: allison
Date: Wed Mar  4 06:31:40 2009
New Revision: 37106
URL: https://trac.parrot.org/parrot/changeset/37106

Log:
[doc] Took a few minutes to update the Metacommitter guide after adding
a committer (an existing committer who just created a Trac account).

Modified:
   trunk/docs/project/metacommitter_guide.pod
   trunk/docs/project/roles_responsibilities.pod

Modified: trunk/docs/project/metacommitter_guide.pod
==============================================================================
--- trunk/docs/project/metacommitter_guide.pod	Wed Mar  4 06:19:23 2009	(r37105)
+++ trunk/docs/project/metacommitter_guide.pod	Wed Mar  4 06:31:40 2009	(r37106)
@@ -1,18 +1,13 @@
-# Copyright (C) 2007, Parrot Foundation.
+# Copyright (C) 2007-2009, Parrot Foundation.
 # $Id$
 
 =head1 Metacommitter Guide
 
-From F<docs/project/roles_responsibilities.pod>:
-
- All Metacommitters are responsible for managing commit access to the Parrot
- repository. Once the Architect or Pumpking approves a request for a
- Contributor to be given commit access, a Metacommitter provides that access.
- The Architect and Pumpking are Metacommitters, but other Project Team members
- may also hold this role.
-
 The procedure below describes how to manage the list of Parrot committers.
 
+See F<docs/project/roles_responsibilities.pod> for more details on the
+various roles in the Parrot project, including the Metacomitter role.
+
 =head2 Instructions the new committer must follow
 
 This procedure must be performed by the new committer before
@@ -22,24 +17,14 @@
 
 =item 1
 
-Create a bitcard.org id with the username you'd like to use
-
-=item 2
-
-Login to L<https://rt.perl.org/rt3/> with the id, so the user name is available
-in RT for assigning tickets, and so it is registered in the list of users
-eligible for parrot commit bit. Your login id is shown at the top of the 
-page, e.g. C<Logged in as coke>. B<This> is the id you must provide to the
-metacommitter so they can add you.
-
-=item 3
-
-Go to L<https://svn.perl.org/accounts/> and follow the directions there to
-setup an svn password for your bitcard account; while the id is the same,
-the passwords are separate.
+Create an account on L<https://trac.parrot.org/parrot>.
 
 =back
 
+You only need to create one account for both the "parrot" and
+"languages" repositories, though the Metacommitter will need to grant
+permissions to the two repositories separately.
+
 =head2 Instructions for the Metacommitter
 
 The new committer must perform the above procedure before
@@ -49,23 +34,43 @@
 
 =item 1
 
-Login to RT at L<https://rt.perl.org/rt3/>
+Login to Trac at L<https://trac.parrot.org/parrot/>
 
 =item 2
 
-Navigate to the Parrot Commit group,
-L<https://rt.perl.org/rt3/Admin/Groups/Members.html?id=178234>
+Navitate to the Admin -> Permissions page,
+L<https://trac.parrot.org/parrot/admin/general/perm>
 
 =item 3
 
-Select the username from the "Add members" listbox, and select
-"Modify Members" button
+If the user is not already in the "developer" group (for access to
+administer tickets), enter the username in the "Add Subject to Group"
+box, and add them to the "developer" group.
+
+
+=item 4
+
+Navigate to the Admin -> Subversion Access page
+L<https://trac.parrot.org/parrot/admin/subversion/svnauthz> and select
+the "parrot_committers" group.
+
+=item 5
+
+Select the username from the "Add Group Member to parrot_commiters"
+listbox, and click the "Add" button. (Note that the username won't
+appear in the drop box until they've been granted "developer"
+permissions.)
 
 =back
 
 Congratulate the new member publicly by sending an email to
 parrot-dev at lists.parrot.org, and copying the new committer.
 
+
+The steps for the "languages" repository and Trac instance are the same,
+except the URLs are L<https://trac.parrot.org/languages/...> and the
+committer group is "languages_committers".
+
 =head2 To manage the list of Metacommitters
 
 Only existing Metacommitters can perform this activity.
@@ -74,8 +79,9 @@
 
 =item 1
 
-navigate to L<https://rt.perl.org/rt3/Admin/Groups/Members.html?id=178219>
-and add/remove users as desired.
+Navigate to the Admin -> Permissions page
+L<https://trac.parrot.org/parrot/admin/general/perm> and add/remove
+"admin" users as desired.
 
 =back 
 
@@ -87,15 +93,14 @@
 
 =item 1
 
-navigate to L<https://rt.perl.org/rt3/Admin/Groups/Members.html?id=20479>
-and add/remove users as desired. Be sure to verify that the userid is the
-one the user shows as logged in as. (Some bugadmins have multiple RT accounts.)
+Navigate to the Admin -> Permissions page
+L<https://trac.parrot.org/parrot/admin/general/perm> and add/remove
+"developer" users as desired.
 
-=back
+Verify that the username is the one the user intends to use to
+administer tickets. (Some bugadmins have multiple Trac accounts.)
 
-=head1 AUTHOR
-
-Jerry Gay a.k.a. particle
+=back
 
 =head1 SEE ALSO
 

Modified: trunk/docs/project/roles_responsibilities.pod
==============================================================================
--- trunk/docs/project/roles_responsibilities.pod	Wed Mar  4 06:19:23 2009	(r37105)
+++ trunk/docs/project/roles_responsibilities.pod	Wed Mar  4 06:31:40 2009	(r37106)
@@ -23,39 +23,24 @@
 for making design decisions and documenting them in Parrot Design Documents;
 responsibility for design and design documentation of project subcomponents
 may be given to other members of the Project Team, or may be held jointly.
-The Architect also works with the Pumpking and Release Managers to develop and
-maintain the release schedule.
-
-=head2 Project Manager
-
-The Project Manager has primary responsibility for tracking project progress.
-The Project Manager holds a weekly meeting with the Project Team and key
-Committers, and reports back to TPF and project sponsors. The Project Manager
-also manages project priorities and developer concerns.
-
-=head2 Pumpking
-
-The Pumpking has primary responsibility for the project source. The Pumpking
-is the lead developer, and as such reviews patches, defines coding standards,
-and assists the efforts of Committers and Contributors. The Pumpking also
-develops and maintains the release schedule with the Architect and Release
-Managers.
+The Architect also works with Release Managers to develop and maintain
+the release schedule.
 
 =head2 Release Manager
 
-Release managers have responsibility for executing a product release,
+Release Managers have responsibility for executing a product release,
 according to the release schedule. The release schedule is developed and
-maintained jointly with the Architect and the Pumpking.
+maintained jointly with the Release Managers and the Architect.
 
 See F<docs/project/release_manager_guide.pod> for more information.
 
 =head2 Metacommitter
 
-All Metacommitters are responsible for managing commit access to the Parrot
-repository. Once the Architect or Pumpking approves a request for a
-Contributor to be given commit access, a Metacommitter provides that access.
-The Architect and Pumpking are Metacommitters, but other Project Team members
-may also hold this role.
+All Metacommitters are responsible for managing commit access to the
+Parrot repository. Once the Architect approves a request for a
+Contributor to be given commit access, a Metacommitter provides that
+access. The Architect is a Metacommitters, but other Project Team
+members also hold this role.
 
 See F<docs/project/metacommiter_guide.pod> for more information.
 
@@ -69,7 +54,7 @@
 
 =head2 Core Developer
 
-Develops and maintains core subsystems (e.g. IO, Exceptions.)
+Develops and maintains core subsystems (e.g. I/O, Exceptions.)
 
 =head2 Compiler Developer
 
@@ -93,7 +78,8 @@
 
 =head2 Platform Porter
 
-Develops and maintains installation packages on various platforms.
+Develops and maintains Parrot for a particular platform, making
+portablility fixes or creating installation packages.
 
 =head2 Patch Monster
 
@@ -122,17 +108,10 @@
 =head2 Cage Cleaner
 
 Fixes failing tests, makes sure coding standards are implemented, reviews
-documentation and examples. A class of tickets in the tracking system (RT) has
-been created for use by this group. This position encompasses tasks from entry
-level to advanced, and is a good way to get familiar with Parrot internals.
-
-=head1 STABILITY
-
-This document is 'Stable'. Changes must be approved by the Project Team.
-
-=head1 AUTHOR
-
-Jerry Gay a.k.a. particle
+documentation and examples. A class of tickets in the tracking system
+(Trac) has been created for use by this group. This position encompasses
+tasks from entry level to advanced, and is a good way to get familiar
+with Parrot internals.
 
 =head1 SEE ALSO
 


More information about the parrot-commits mailing list