[ros-dev] Constitution

Murphy, Ged (Bolton) MurphyG at cmpbatteries.co.uk
Mon Oct 17 10:48:00 CEST 2005

This sounds reasonable.
Phpbb can use the feature whereby only a set group can post in a certain
section of the forum, in this case, the developer group in the voting

This also gives the added bonus of being a secret ballot, as Ge requested.

Comments can be made without polluting the topic, and the results can be
written to the wiki.

-----Original Message-----
From: Freworld [mailto:michael at freeworld.net] 
Sent: 17 October 2005 09:19
To: ReactOS Development List
Subject: Re: [ros-dev] Constitution

Perhaps we should vote on the website rather than on the mailinglist? 
The mailinglist could be used for the discussion about what exactly the 
vote will be and to make the vote public with a link (most people don't 
look at the website but at the mailinglist). With the new login system 
it would be no problem to control that only committers can vote. This 
way we would have a clean overlook what decisions were taken and what 
was decided exactly.

If there is an interest in this I would implement it into the website.


Casper Hornstrup wrote:

>>-----Original Message-----
>>From: ros-dev-bounces at reactos.org [mailto:ros-dev-bounces at reactos.org] On
Behalf Of Ge van Geldorp
>>Sent: 16. oktober 2005 23:56
>>To: 'ReactOS Development List'
>>Subject: RE: [ros-dev] Constitution
>>Looks good. A few comments:
>>The Registered Project Members can (by General Resolution) override any
>>decision made by the Project Coordinator or the Area Coordinators.
>>the Repository Coordinator and Project Secretary can make decisions
>>"preferably consistent with the consensus of the Project Members". It
>>to me that Registered Project Members should be able to override their
>>decisions too.
>[CSH] Right. How about changing:
>* Override any decision made by the Project Coordinator or Area
>* Appoint or dismiss the Project Coordinator or Area Coordinator.
>* Override any decision made by the Project Secretary or any Coordinator.
>* Appoint or dismiss the Project Secretary or any Coordinator.
>>There is a mandatory 1 week discussion period and 1 week voting period for
>>each vote, with no escape clause. For some votes (whether to release or
>>comes to mind) 2 weeks seems a bit long. Can we change it so that the
>>proposer can ask for shorter periods, with a safeguard that the shorter
>>periods will be denied if a single Registered Project Member objects?
>[CSH] I thought of having a "quick vote" for decisions which are needed
>and now (like whether or not to release now) and not necessarily need to be
>documented anywhere else than the mailing lists for future reference, but
>would you define the two?
>Maybe we could allow the Registered Project Member that calls for the vote
>choose any number of days of voting period less than 7 days, but at least
>days and no discussion period? Any Registered Project Member already has
>right to demand a revote at any time (maybe there should be some protection
>from abuse of that right? One could spam until he/she gets what he/she
>>I really would like Coordinator Elections to be secret (or private, not
>>what the correct English term is). I should be able to cast my vote
>>the candidates knowing on who (or even if) I voted. I believe this should
>>explicitly mentioned in the Coordinator Elections voting procedure.
>>Ge van Geldorp.
>[CSH] We haven't done secret elections before. I could go either way. If
>secret then you put a lot of power into one person, the person that
>the votes (most likely the Project Secretary). What procedure would you
>Ros-dev mailing list
>Ros-dev at reactos.org

Ros-dev mailing list
Ros-dev at reactos.org
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster at exideuk.co.uk 
<mailto:postmaster at exideuk.co.uk> and then delete this message. 

Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com

More information about the Ros-dev mailing list