Organization
From OpenSimulator
(New page: The OpenSimulator project is fueled by a small group of core developers who produce the bulk of the code and who have commit access to the GIT repository. These core developers are respons...) |
|||
| Line 1: | Line 1: | ||
| − | The OpenSimulator project is fueled by a small group of core developers who produce the bulk of the code and who have commit access to the GIT repository. These core developers are responsible for deciding what goes in the main distribution, and for inviting new developers to the core group. A much larger community of developers, testers, and users makes the OpenSimulator code come to life in all sorts of colorful and enhanced ways. Without this large community, this project | + | The OpenSimulator project is fueled by a small group of core developers who produce the bulk of the code and who have commit access to the GIT repository. These core developers are responsible for deciding what goes in the main distribution, and for inviting new developers to the core group. A much larger community of developers, testers, and users makes the OpenSimulator code come to life in all sorts of colorful and enhanced ways. Without this large community, this project wouldn't exist. |
| − | Membership in the core developers group is by invitation | + | Membership in the core developers group is by invitation. The criteria for invitation is based on demonstrated skills in being able to produce interesting and useful code within the very large main code base, in being able to handle some degree of pressure gracefully, and in being able to function within the multi-faceted spirit of the project. |
Core developers who go for 6 or more months without contributing code are changed to a status called "chasing the white rabbit". This status is in all similar to the active status, except that these developers don't participate in the decisions. As soon as these developers start committing code again, they are moved back into active status. At their request, these white rabbit chasers are moved to a permanently disengaged status, loosing their access to the repository server. | Core developers who go for 6 or more months without contributing code are changed to a status called "chasing the white rabbit". This status is in all similar to the active status, except that these developers don't participate in the decisions. As soon as these developers start committing code again, they are moved back into active status. At their request, these white rabbit chasers are moved to a permanently disengaged status, loosing their access to the repository server. | ||
Revision as of 11:27, 23 September 2011
The OpenSimulator project is fueled by a small group of core developers who produce the bulk of the code and who have commit access to the GIT repository. These core developers are responsible for deciding what goes in the main distribution, and for inviting new developers to the core group. A much larger community of developers, testers, and users makes the OpenSimulator code come to life in all sorts of colorful and enhanced ways. Without this large community, this project wouldn't exist.
Membership in the core developers group is by invitation. The criteria for invitation is based on demonstrated skills in being able to produce interesting and useful code within the very large main code base, in being able to handle some degree of pressure gracefully, and in being able to function within the multi-faceted spirit of the project.
Core developers who go for 6 or more months without contributing code are changed to a status called "chasing the white rabbit". This status is in all similar to the active status, except that these developers don't participate in the decisions. As soon as these developers start committing code again, they are moved back into active status. At their request, these white rabbit chasers are moved to a permanently disengaged status, loosing their access to the repository server.
