User:Mlforcada/sandbox/governance - Revision history

172.16.242.124: /* Project Management Committee */

2010-02-24T13:52:48Z

Project Management Committee

172.16.242.124: /* Project Management Committee */

2010-02-24T13:52:05Z

Project Management Committee

172.16.242.124: /* Project Management Committee */

2010-02-24T13:47:39Z

Project Management Committee

172.16.242.124: /* Users */

2010-02-24T08:09:35Z

Users

172.16.242.124: /* Project Management Committee */

2010-02-24T08:05:02Z

Project Management Committee

172.16.242.124: /* The assembly of committers */

2010-02-24T08:00:24Z

The assembly of committers

Jimregan: /* Mission */ rm 'shallow-transfer', cf. Juan Antonio's email

2010-02-23T13:10:02Z

Mission: rm 'shallow-transfer', cf. Juan Antonio's email

Jacob Nordfalk: /* Developers */

2010-02-22T08:30:02Z

Developers

Francis Tyers: /* Project Management Committee */

2010-02-14T12:23:29Z

Project Management Committee

Francis Tyers: /* The assembly of committers */

2010-02-14T12:20:42Z

The assembly of committers

@@ Line 44: / Line 44: @@
 ## Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.
 ## Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.
-## Speaking on behalf of the project; Although, the PMC could exceptionally give the right to speak on behalf of Apertium to a member of the Assembly of Commiters.
+## Speaking on behalf of the project; although, the PMC could exceptionally give the right to speak on behalf of Apertium to a member of the Assembly of Commiters.
 ## Resolving licence disputes regarding products of the project.
 ## Giving access rights to new Committers.

@@ Line 44: / Line 44: @@
 ## Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.
 ## Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.
-## Speaking on behalf of the project.
+## Speaking on behalf of the project; Although, the PMC could exceptionally give the right to speak on behalf of Apertium to a member of the Assembly of Commiters.
 ## Resolving licence disputes regarding products of the project.
 ## Giving access rights to new Committers.

@@ Line 53: / Line 53: @@
 # The Project Management Committee votes on all of its decisions. The President has the casting vote.
 # The Project Management Committee has the obligation to submit to the Assembly of Committers the decisions that affect the work of the half or more of the members of the Assembly of Committers, being able to consult in other subjects if like this believed it necessary.
-# Decisions of the Project Management Committee made other than in consultation with the Assembly are filed in a diary and are periodically presented to the Assembly of Committers, which approves them or rejects them. The period between cannot be longer than six months.
+# Decisions of the Project Management Committee made other than in consultation with the Assembly are filed in a diary and are periodically presented to the Assembly of Committers, which approves them or rejects them. The period between cannot be longer than three months.
 # The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Committers.

@@ Line 17: / Line 17: @@
 # The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective.
-# Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users on the mailing list and in the chat channel
+# Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.
 === Developers ===

@@ Line 53: / Line 53: @@
 # The Project Management Committee votes on all of its decisions. The President has the casting vote.
 # The Project Management Committee has the obligation to submit to the Assembly of Committers the decisions that affect the work of the half or more of the members of the Assembly of Committers, being able to consult in other subjects if like this believed it necessary.
-# Decisions of the Project Management Committee made other than in consultation with the Assembly are filed in a diary and are periodically presented to the Assembly of Committers, which approves them or rejects them. The period between cannot be longer than a month.
+# Decisions of the Project Management Committee made other than in consultation with the Assembly are filed in a diary and are periodically presented to the Assembly of Committers, which approves them or rejects them. The period between cannot be longer than six months.
 # The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Committers.

@@ Line 31: / Line 31: @@
 # One tenth of the Assembly of Commiters may propose a motion of censure to overturn the Project Management Committee, which has to be approved by half plus one of the members of the Assembly of Committers
 # The number of members of the Assembly of Committers of Apertium does not have any limit.
-# Committer access is by received by committing code and getting sponsorship by two existing Committers, a nominator and a seconder. Upon fulfillment of these conditions, a PMC member will give write access.
+# Committer access is received by committing code and getting sponsorship by two existing Committers, a nominator and a seconder. Upon fulfillment of these conditions, a PMC member will give write access.
 # A Committer is considered emeritus by their own declaration or by not contributing in any form to the project for over six months. An emeritus committer may request reinstatement of commit access from the PMC.
 # The president and the secretary of the Project Management Committee will also act as President and Secretary of the assembly of committers

@@ Line 7: / Line 7: @@
 # The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:
 ## To give everyone free, unlimited access to the best possible machine-translation technologies.
-## To maintain a modular, documented, open platform for shallow-transfer machine translation and other human language processing tasks
+## To maintain a modular, documented, open platform for machine translation and other human language processing tasks
 ## To favour the interchange and reuse of existing linguistic data.
 ## To make integration with other free/open-source technologies easier.

@@ Line 21: / Line 21: @@
 === Developers ===
-# Developers are  volunteers who are contributing time, code, documentation, or resources to Apertium. A developer that makes sustained, welcome contributions to the project may be invited to become a committer, though the exact timing of such invitations depends on many factors
+# Developers are  volunteers who are contributing time, code, documentation, or resources to Apertium. A developer that makes sustained, welcomed contributions to the project may be invited to become a committer, though the exact timing of such invitations depends on many factors
 === The assembly of committers ===

@@ Line 46: / Line 46: @@
 ## Speaking on behalf of the project.
 ## Resolving licence disputes regarding products of the project.
-## Nominating new Committers.
+## Giving access rights to new Committers.
-{{comment|:I would make this "adding new committers" - [[User:Francis Tyers|Francis Tyers]]}}
 ## Maintaining these bylaws and other guidelines of the project.
 ## Promoting the active engagement of Apertium in larger free/open-source initiatives