Actions

Difference between revisions of "Team member administration"

From Joomla! Documentation

(Bug Squad administration)
(Development team administration)
Line 14: Line 14:
 
== Development team administration ==
 
== Development team administration ==
  
Members of the development team have full commit access to the Joomla! subversion repository. This is one of the main differences between [Bug Squad] and development team members. In short member of the [Development Team] have the following infrastructure:
+
Members of the development team have full commit access to the Joomla! subversion repository. This is one of the main differences between [[Bug Squad]] and development team members. In short member of the [[Development Team]] have the following infrastructure:
  
 
* Access to the private Joomla! forum. We keep track on personal details of members, but also private discussions can take place here (security talks, or private development matters).
 
* Access to the private Joomla! forum. We keep track on personal details of members, but also private discussions can take place here (security talks, or private development matters).
 
* Full access to the Joomla! subversion repository. These access rights are granted with adding the developer with his Joomlacode account, and connect him to the profile of "Development Team Member" (admin access to Gforge for the Joomla! project is required).
 
* Full access to the Joomla! subversion repository. These access rights are granted with adding the developer with his Joomlacode account, and connect him to the profile of "Development Team Member" (admin access to Gforge for the Joomla! project is required).
 
* Full access to the Joomla! development[http://www.example.com  working group mailing list]. You can send a request to be added, or ask the development working group coordinator.
 
* Full access to the Joomla! development[http://www.example.com  working group mailing list]. You can send a request to be added, or ask the development working group coordinator.
* Option access (on request) to the [http://groups.google.com/group/joomlabugsquad Joomla! bug squad mailing list]. You can send a request to be added, or ask the development working group coordinator, or the team leader(s) of the [Bug Squad].
+
* Option access (on request) to the [http://groups.google.com/group/joomlabugsquad Joomla! bug squad mailing list]. You can send a request to be added, or ask the development working group coordinator, or the team leader(s) of the [[Bug Squad]].
  
For the (team) manager in charge, there is a checklist for adding members to the [Development Team], please read the [Development Team Checklist].
+
For the (team) manager in charge, there is a checklist for adding members to the [[Development Team]], please read the [[Development Team Checklist]].

Revision as of 03:25, 23 May 2008

The development team currently holds two teams; the [Bug Squad] and the [Development Team].

[Bug Squad] members have different access rights, and have also different access to the infrastructure we offer. In this document the specific infrastructure is described per team.


Bug Squad administration

Members of the [Bug Squad] have access to the following infrastructure components:

  • Access (on request) to the Joomla! bug squad mailing list. You can send a request to be added, or ask the development working group coordinator, or the team leader(s) of the [Bug Squad].

For the (team) manager in charge, there is a checklist for adding members to the [Bug Squad], please read the Bug Squad Checklist.

Development team administration

Members of the development team have full commit access to the Joomla! subversion repository. This is one of the main differences between Bug Squad and development team members. In short member of the Development Team have the following infrastructure:

  • Access to the private Joomla! forum. We keep track on personal details of members, but also private discussions can take place here (security talks, or private development matters).
  • Full access to the Joomla! subversion repository. These access rights are granted with adding the developer with his Joomlacode account, and connect him to the profile of "Development Team Member" (admin access to Gforge for the Joomla! project is required).
  • Full access to the Joomla! developmentworking group mailing list. You can send a request to be added, or ask the development working group coordinator.
  • Option access (on request) to the Joomla! bug squad mailing list. You can send a request to be added, or ask the development working group coordinator, or the team leader(s) of the Bug Squad.

For the (team) manager in charge, there is a checklist for adding members to the Development Team, please read the Development Team Checklist.