Organization
From OpenSimulator
| Line 1: | Line 1: | ||
OpenSimulator core developers are those individuals who have direct access to the OpenSimulator source code 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. | OpenSimulator core developers are those individuals who have direct access to the OpenSimulator source code 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, where all existing active core developers must be in agreement. The chief criteria for invitation are | |
| − | # Demonstrated skill in resolving bugs or adding useful code to the main code base which is consistent with the existing code. | + | # Demonstrated skill in resolving bugs or adding useful code to the main code base which is consistent with the existing code. |
# Being prepared to listen and take action in response to constructive criticism of code patches. | # Being prepared to listen and take action in response to constructive criticism of code patches. | ||
| + | # Being willing to fix any regressions that their work introduces. | ||
# Being available regularly by IRC and e-mail to directly answer questions about code and for on-going co-operation with other core developers. | # Being available regularly by IRC and e-mail to directly answer questions about code and for on-going co-operation with other core developers. | ||
# Working well with others. | # Working well with others. | ||
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, losing 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, losing their access to the repository server. | ||
Revision as of 16:58, 29 November 2013
OpenSimulator core developers are those individuals who have direct access to the OpenSimulator source code 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, where all existing active core developers must be in agreement. The chief criteria for invitation are
- Demonstrated skill in resolving bugs or adding useful code to the main code base which is consistent with the existing code.
- Being prepared to listen and take action in response to constructive criticism of code patches.
- Being willing to fix any regressions that their work introduces.
- Being available regularly by IRC and e-mail to directly answer questions about code and for on-going co-operation with other core developers.
- Working well with others.
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, losing their access to the repository server.
