cdg: regulations.txt - more 1:1 translation - also, the ancient art of a sp...

[mmazur]

Author: mmazur                       Date: Thu Jan 27 23:48:14 2011 GMT
Module: cdg                           Tag: HEAD
---- Log message:
- more 1:1 translation
- also, the ancient art of a spell checker came in handy
- didn't proof-read, so might still have some errors

---- Files affected:
cdg:
   regulations.txt (1.10 -> 1.11) 

---- Diffs:

================================================================
Index: cdg/regulations.txt
diff -u cdg/regulations.txt:1.10 cdg/regulations.txt:1.11
--- cdg/regulations.txt:1.10	Thu Jan 27 14:32:16 2011
+++ cdg/regulations.txt	Fri Jan 28 00:48:09 2011
@@ -4,18 +4,18 @@
 Core-Developers-Group
 ~~~~~~~~~~~~~~~~~~~~~
 
-The Core Developers Group operates on behalf of the PLD Linux Distribution.
-CDG makes decisions democratically. The CDG is responsible for making
-decisions that are critical for the distribution and for solving conflicts
-among the management.
+The Core Developers Group operates on behalf and in the interest 
+of the PLD Linux Distribution. CDG makes decisions in a democratic
+fashion. CDG is responsible for making decisions that are critical
+to the distribution and for resolving conflicts.
 
-CDG members are appointed by general ellection. Belinging to the CDG is
-the second stage of developer status (after being granted RW).
+CDG can be seen as a general election and belonging to it as
+the second stage of being a developer (after being granted RW).
 
 
 *** Conflicts.
 
-CDG is able to make decisions which cannot be made by other developers
+CDG is able to make decisions which cannot be made by interested developers
 in the course of discussion. For example:
   1. Revoking somebody's RW in CVS
   2. Disputes about the contents of a specific specfile
@@ -23,66 +23,76 @@
 
 *** Decisions.
 
-Decisions about issuing sequential versions of the distribution and the
-timing.
+Decisions regarding the facts and dates of new PLD releases.
 
 
 *** Membership.
 
-The admision/removal of a CDG member is accomplished by a 2/3 majority
+The admission/removal of a CDG member is accomplished by a 2/3 majority
 vote with a minimum of 50% turnout. Only CDG members vote.
 
 A proposal for removing a member is to be voted on after 3 months of
-that members inactivity as a CDG (lack of comments, no voting, etc.).
+that member's inactivity within CDG (lack of comments, no voting, etc.).
 
 A CDG member may resign. This does not require a vote.
 
 A member who temporarily cannot participate in CDG activities may choose
-to suspend themselves. This is done by adding the text ":suspended till
+to suspend himself. This is done by adding the text ":suspended till
 <date>" after their login in sklad.txt. Suspension is effective the next
-day (by UTC time) after commiting the entry and lasts until the specified
-day. A member may return to the CDG earlier by removing the suspention
+day (by UTC time) after committing the entry and lasts until the specified
+day. A member may return to the CDG earlier by removing the suspension
 entry from the file - in which case the last day of suspension is the day
-prior (according to the UTC timezome) to removing the entry. During
+prior (according to the UTC timezone) to removing the entry. During
 suspension:
 - the member is not counted idle as defined in the Membership section.
-- the member is not taken into account when calculating a quarum for a
+- the member is not taken into account when calculating a quorum for a
   vote held entirely inside of the suspension period.
 The total period of suspension must not exceed six months during a
 calendar year.
 
 Withdrawal from CDG does not imply the revoking of RW access.
 
-A list of active CDG members can be found in "sklad.txt"
 
 *** Voting.
 
 A proposal for a vote may be filled by any PLD developer (not just
-mebmers of the CDG). The proposal must stay in CVS for at least 24h
+members of the CDG). The proposal must stay in CVS for at least 24h
 during which time it should be discussed and, if needed, modified.
 
-A proposal must be seconded by three members of the CDG before being
-taken to a vote. If a proposal does not gain enough support in the 30
-days following being filed it is automatically withdrawn. A proposal may
-also be withdrawn by its author provided that the voting phase has not
-yet begun.
+Afterwards, the proposal must be seconded by three members of the CDG,
+which allows the voting to begin. If a proposal does not gain enough support
+in the 30 days following being filled, it is automatically withdrawn. A
+proposal may also be withdrawn by its author provided that the voting phase
+has not yet begun.
+
+The vote proposal must be written in a language/languages, which make it
+understandable to all members of CDG. So if, for example, a CDG
+member does not speak Polish, one of the languages the proposal must be
+written in should be a language understandable by that person. On a
+similar note, if all members of CDG declare that they understand
+English, it can be the only language a proposal is written in. The
+translation must be done before the vote begins (not necessarily during
+the initial commit, might be also later, during discussions or
+seconding).
 
 Voting is accomplished in the cdg cvs module
-(cvs://cvs.pld-linux.org/cdg/). Voting is public and notes maybe changed
-during the duration of the voting phase. CDG members may also cast
-their votes by sending a PGP-signed email to the CDG mailing list. The
-public key should be placed in the PGP-keys module on the cvs server.
-
-The voting period is 48h from the time it is announced on the list. In
-the event of an insufficient turnout, voting may be extened for another
-48h to a maximum of three extentions.
+(cvs://cvs.pld-linux.org/cdg/). Voting is public and votes may be changed
+over the duration of the voting phase. CDG members may also cast
+their votes by sending a PGP-signed email to the CDG mailing list. Such
+votes must be signed by a PGP key, of which the public key has been
+already placed inside the PGP-keys module on the cvs server.
+
+The voting period is 48h from the time specified in the announced on the
+list. In the event of an insufficient turnout, voting may be extended for another
+48h to a maximum of three extensions.
 
-After the completion of voting, uncast votes are treated as abstentions.
+After the completion of voting, the votes that weren't cast are treated
+as abstentions.
 
 Changes to these regulations or modifications to the membership of CDG
 require the number of YES votes to be at least twice as high as the
 number of NO votes, a minimum turnout of at least 50% and at least one
-non-abstain vote.
+non-abstaining vote.
 
 All other votes require a simple majority of votes, regardless of the
 turnout.
================================================================

---- CVS-web:
    http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/cdg/regulations.txt?r1=1.10&r2=1.11&f=u