Organization - Revision history

Manni at 10:16, 4 December 2023

2023-12-04T10:16:36Z

Acryline at 09:35, 20 November 2021

2021-11-20T09:35:01Z

Steevithak: /* Membership */ fixed a couple of typos

2020-09-24T14:40:45Z

‎Membership: fixed a couple of typos

Steevithak: added link to orphaned Infrastructure page

2020-09-06T21:38:11Z

added link to orphaned Infrastructure page

Aiaustin: /* Membership */ missing word "respects" added

2020-01-07T17:03:52Z

‎Membership: missing word "respects" added

Justincc: /* Membership */

2015-01-05T19:27:34Z

‎Membership

Justincc: /* Etiquette */

2014-03-20T23:53:11Z

‎Etiquette

Justincc: Update organization page with core developers expected to be on IRC

2014-03-20T23:48:53Z

Update organization page with core developers expected to be on IRC

Justincc at 01:01, 30 November 2013

2013-11-30T01:01:07Z

Justincc at 00:59, 30 November 2013

2013-11-30T00:59:46Z

← Older revision		Revision as of 10:16, 4 December 2023
Line 1:		Line 1:
−	{{Quicklinks}}	+	{{Quicklinks\|Organization}}
	=General=		=General=

← Older revision		Revision as of 09:35, 20 November 2021
Line 1:		Line 1:
		+	{{Quicklinks}}
	=General=		=General=

@@ Line 10: / Line 10: @@
 =Membership=
-Membership in the core developers group is by invitation, where all existing active core developers must either be in support or neutral.  Any core developer can veto the addition of a new member, though they then must be prepared to give convincing reasons for that veto.  The chief criteria for invitation are
+Membership in the core developers group is by invitation, where all existing active core developers must either be in support or neutral.  Any core developer can veto the addition of a new member, though they then must be prepared to give convincing reasons for that veto.  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.
@@ Line 19: / Line 19: @@
 # Working well with others.
-One somebody becomes a core developer, they gain equal rights to everybody else on the project.  This includes the ability to introduce new code as they see fit and the right to veto proposed new members.
+Once somebody becomes a core developer, they gain equal rights to everybody else on the project.  This includes the ability to introduce new code as they see fit and the right to veto proposed new members.
-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 respects 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 respects 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 to active status. At their request, these white rabbit chasers are moved to a permanently disengaged status, losing their access to the repository server.
 =Infrastructure=
 The development process is facilitated by resources such code repositories, bug databases, mailing lists, IRC channels, and this Wiki. For more details, see [[Infrastructure|OpenSimulator Infrastructure]].

← Older revision		Revision as of 21:38, 6 September 2020
Line 22:		Line 22:

	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 respects 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 respects 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.
		+
		+	=Infrastructure=
		+	The development process is facilitated by resources such code repositories, bug databases, mailing lists, IRC channels, and this Wiki. For more details, see [[Infrastructure\|OpenSimulator Infrastructure]].

← Older revision		Revision as of 17:03, 7 January 2020
Line 21:		Line 21:
	One somebody becomes a core developer, they gain equal rights to everybody else on the project. This includes the ability to introduce new code as they see fit and the right to veto proposed new members.		One somebody becomes a core developer, they gain equal rights to everybody else on the project. This includes the ability to introduce new code as they see fit and the right to veto proposed new members.

−	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 respects 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.

@@ Line 13: / Line 13: @@
 # 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.
+# Demonstrated competence in several OpenSimulator features.
-# Being willing to fix any regressions that their work introduces.
+# Listening taking action in response to constructive criticism of code patches.
 # 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.

← Older revision		Revision as of 23:53, 20 March 2014
Line 6:		Line 6:

	As well as following the [[Contributions_Policy#OpenSimulator_Core_Values\|general project expectations]], core developers are expected to be present on IRC when they add code to the repository, so that any immediate issues can be highlighted and resolved.		As well as following the [[Contributions_Policy#OpenSimulator_Core_Values\|general project expectations]], core developers are expected to be present on IRC when they add code to the repository, so that any immediate issues can be highlighted and resolved.
		+
		+	A private IRC and mailing list exist for the core group. However, these should only be used for communication about core group membership, security issues and other similar topics. All technical and other project conversation should take place on the normal OpenSimulator mailing lists and IRC channels.

	=Membership=		=Membership=

← Older revision		Revision as of 23:48, 20 March 2014
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.	+	=General=

		+	OpenSimulator core developers are those individuals who have direct access to the OpenSimulator source code repository. They are responsible for deciding what goes in the project 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 extended community, this project wouldn't exist.
		+
		+	=Etiquette=
		+
		+	As well as following the [[Contributions_Policy#OpenSimulator_Core_Values\|general project expectations]], core developers are expected to be present on IRC when they add code to the repository, so that any immediate issues can be highlighted and resolved.
		+
		+	=Membership=
	Membership in the core developers group is by invitation, where all existing active core developers must either be in support or neutral. Any core developer can veto the addition of a new member, though they then must be prepared to give convincing reasons for that veto. The chief criteria for invitation are		Membership in the core developers group is by invitation, where all existing active core developers must either be in support or neutral. Any core developer can veto the addition of a new member, though they then must be prepared to give convincing reasons for that veto. The chief criteria for invitation are

@@ 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.
-Membership in the core developers group is by invitation, where all existing active core developers must either be in support or neutral.  The chief criteria for invitation are
+Membership in the core developers group is by invitation, where all existing active core developers must either be in support or neutral.  Any core developer can veto the addition of a new member, though they then must be prepared to give convincing reasons for that veto.  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.