User:ScoopGracie/PMC/Proposed bylaws - Revision history

ScoopGracie at 21:40, 22 March 2020

2020-03-22T21:40:06Z

ScoopGracie at 21:19, 22 March 2020

2020-03-22T21:19:29Z

ScoopGracie: Change it to something more easily calculable

2020-03-22T20:47:46Z

Change it to something more easily calculable

ScoopGracie: Undo revision 71222 by ScoopGracie (talk)

2020-03-18T19:07:21Z

Undo revision 71222 by ScoopGracie (talk)

ScoopGracie: /* Project Management Committee */

2020-03-17T16:06:53Z

Project Management Committee

ScoopGracie at 23:11, 14 March 2020

2020-03-14T23:11:28Z

ScoopGracie at 22:04, 14 March 2020

2020-03-14T22:04:27Z

ScoopGracie: /* Transitional provisions */

2020-03-14T21:57:54Z

Transitional provisions

ScoopGracie: /* Amendments */

2020-03-14T21:57:34Z

Amendments

ScoopGracie: /* Election of the Project Management Committee */

2020-03-14T21:54:12Z

Election of the Project Management Committee

@@ Line 95: / Line 95: @@
 <li>There will be 7 days to send the ballots</li>
 <li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li>
-<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li>
+<li>The new Project Management Committee will start to function 48 hours after being proclaimed.</li>
 </li>
 </ol></li>

@@ Line 29: / Line 29: @@
 <ol start="3">
 <li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li>
-<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past twenty-four weeks (168 days, or approximately six months).</li>
+<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least one pull request or commit to any Apertium repository in the past twenty-four weeks (168 days, or approximately six months).</li>
 <li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li>
 <li>The project's Developers are responsible for the project's technical management.</li>
@@ Line 37: / Line 37: @@
 <li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li>
 <li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li>
-<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li>
+<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by three fourths of the Developers.</li>
 </ol>

@@ Line 29: / Line 29: @@
 <ol start="3">
 <li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li>
-<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li>
+<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past twenty-four weeks (168 days, or approximately six months).</li>
 <li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li>
 <li>The project's Developers are responsible for the project's technical management.</li>

@@ Line 63: / Line 63: @@
 <li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li>
 <li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li>
-<li>If a member of the PMC decides to participate in Google Summer of Code or Google Code-in, that member shall temporarily resign. His/her space on the PMC will be held until GSoC/GCI is over.
 </ol>

@@ Line 63: / Line 63: @@
 <li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li>
 <li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li>
+<li>If a member of the PMC decides to participate in Google Summer of Code or Google Code-in, that member shall temporarily resign. His/her space on the PMC will be held until GSoC/GCI is over.
 </ol>

@@ Line 1: / Line 1: @@
 '''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!
+== Preamble ==
+The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:
-== Mission ==
-<ol start="1">
-<li>The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:
 <ol style="list-style-type:lower-alpha" >
 <li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li>
@@ Line 17: / Line 14: @@
 <li>To help combat gender and racial bias in technology.</li>
 <li>To help support and preserve less widespread languages.</li>
-</ol>
-</li>
 </ol>
@@ Line 25: / Line 20: @@
 === Users ===
-<ol start="2">
+<ol start="1">
 <li>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</li>
 <li>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.</li>
@@ Line 32: / Line 27: @@
 === Developers ===
-<ol start="4">
+<ol start="3">
 <li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li>
 <li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li>
@@ Line 47: / Line 42: @@
 === Project Management Committee ===
-<ol start="14">
+<ol start="13">
 <li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li>
 <li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li>
@@ Line 64: / Line 59: @@
 <li>The Project Management Committee votes on all of its decisions.</li>
 <li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li>
-<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 13.</li>
+<li>Decisions of the PMC are accepted or rejected by the President of the Assembly of Committers, but the PMC may pass a decision despite rejection by the President of the Assembly of Developers with the agreement of five members.</li>
+<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 12.</li>
 <li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li>
 <li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li>
@@ Line 114: / Line 110: @@
 <ol start="31">
-<li>Bylaw 13 does not apply to the acceptance of these bylaws.</li>
+<li>Bylaw 12 does not apply to the acceptance of these bylaws.</li>
-<li>Bylaw 13 does not apply to decisions made by the Project Management Committee or Assembly of Committers under the previous Bylaws. These may only be overturned by a replacement decision made using the standard process under these Bylaws.</li>
+<li>Bylaw 12 does not apply to decisions made by the Project Management Committee or Assembly of Committers under the previous Bylaws. These may only be overturned by a replacement decision made using the standard process under these Bylaws.</li>
 </ol>

@@ Line 64: / Line 64: @@
 <li>The Project Management Committee votes on all of its decisions.</li>
 <li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li>
-<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 15.</li>
+<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 13.</li>
 <li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li>
 <li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li>
@@ Line 73: / Line 73: @@
 <li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li>
 <li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li>
+<li>All members of the Bylaw Violation Court shall agree to a Pledge of Non-bias, as follows:
+<br>
+I, <name>, hereby pledge that I will not act in my own personal interest, in the interest of the accused Developer, or in the interest of the accuser(s), but in the interest of the Apertium project as a whole. My decisions will not be biased based on who the accused or accusing Developer(s) is/are.</li>
 <li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li>
 </ol>
@@ Line 78: / Line 81: @@
 == Election of the Project Management Committee ==
-<ol start="26">
+<ol start="27">
 <li>The Assembly of Developers will elect a new Project Management Committee as follows:
 <ol style="list-style-type:lower-alpha" >
@@ Line 102: / Line 105: @@
 == Amendments ==
-<ol start="27">
+<ol start="28">
 <li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li>
 <li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li>
@@ Line 110: / Line 113: @@
 == Transitional provisions ==
-<ol start="30">
+<ol start="31">
-<li>Bylaw 15 does not apply to the acceptance of these bylaws.</li>
+<li>Bylaw 13 does not apply to the acceptance of these bylaws.</li>
-<li>All PMC or Assembly decisions made prior to the acceptance of these bylaws are final, and Bylaw 15 does not apply to these decisions.</li>
+<li>Bylaw 13 does not apply to decisions made by the Project Management Committee or Assembly of Committers under the previous Bylaws. These may only be overturned by a replacement decision made using the standard process under these Bylaws.</li>
 </ol>