Anthony Towns <aj@azure.humbug.org.au> writes:
> =====
> 5.2. Appointment
>
> 1. The Project Leader is elected by the Developers.
> 2. The election begins [-nine-] {+six+} weeks before the leadership
> post becomes vacant, or (if it is too late already) immediately.
> 3. For the [-following three weeks-] {+first week+} any Developer
> may nominate themselves as a candidate Project [-Leader.-]
> {+Leader, and summarise their plans for their term.+}
> 4. For three weeks after that no more candidates may be nominated;
> candidates should use this time for campaigning [-(to make their
> identities-] and [-positions known).-] {+discussion.+} If there
> are no candidates at the end of the nomination period then the
> nomination period is extended for [-three further weeks,-] {+an
> additional week,+} repeatedly if necessary.
> 5. The next [-three-] {+two+} weeks are the polling period during
> which Developers may cast their votes. Votes in leadership
> elections are kept secret, even after the election is finished.
> 6. The options on the ballot will be those candidates who have
> nominated themselves and have not yet withdrawn, plus None Of The
> Above. If None Of The Above wins the election then the election
> procedure is repeated, many times if necessary.
> 7. The decision will be made using the method specified in section
> A.6 of the Standard Resolution Procedure. The quorum is the same
> as for a General Resolution (4.2) and the default option is "None
> Of The Above".
> 8. The Project Leader serves for one year from their election.
> =====
Seconded. This was overdue.
Marc
--
Fachbegriffe der Informatik - Einfach erklärt
31: Multimedia-Multitasking
CD-ROM mit Kopfhöreranschluß. (VOBIS Denkzettel)
Attachment:
pgprJLipw2j_c.pgp
Description: PGP signature