1. Installation of a democratic voting system for the MCF project 2. Ranking system

Hi,

i am adressing you with a request for something that is very necessary IMHO for 
every opensource project, and its about time i think we start installing such for MCF 
also.

Steve informed me yesterday that there is a big number of spec changes pending, 
and although he is 'chief developer' of the project right now he doesnt want to make 
all these decisions alone by himself, but wants to have them confirmed by all other 
team members.

In addition to that we are working on a new homepage and we have 2 or 3 different 
approaches here, and the team should make a decision about this issue either.

Also i am convinced that we should start to implement 'responsibilities' to certain 
people, maybe also coming along with 'titles'  ( lol :-) ), but this is just an option.



1. Here is my draft for a regulation of a MCF voting system :


a. A new Mailing list will be generated called 'MCF-vote' . This list is only used to

- submit decisions to the voting process
- vote on submitted processes

No discussion is going there !

There will be no access to this list via NNTP, so all members have to subscribe to it 
to be able to participate in the vote.


b. A list of 'active' MCF team members should be held. All members on this list, and 
only them, are allowed to participate in votes.

Other people, being not on this list, can vote ( we cant prevent them ), but their votes 
will not be counted for the end result.

My proposition for such a list ( October 2002 ) :

robux4
Tronic
myFUN
spyder482
milkman.dan
mf
sysKin
ChristianHJW
BlackSun


Potential members ( we should ask them by time if they want to become team 
members ) :

Ingo
Foogod
shatty
mmu_man
hikke
SmokesLikeAPoet
MTRH
GomGom
suxen_drol
de_xt
avih
Betaboy
Ciler
Oxygen

Did i forget anybody ?


c. Every team member can submit a decision for voting to the list. Each vote will run 
for 1 week. If no more than 3 votes are counted for the vote during this time it is 
declared insufficient, and its decision of the submittant if he wants to repeat it or not.

Every vote has to be clear and can only have 2 or 3 options to be decided between !


d. Every member voting to a pending decision has to be capable to understand the 
subject completely. This is to prevent that non-technical people vote although they 
don't understand the background of the question.
If a vote as a technical and a non-technical background it has to be separated into 2 
votes.
Its the right of the submittant of the vote to check with everybody who voted if he has 
understood what the vote was about, by inviting him to the IRC channel and asking 
questions about the subject. If its becoming obvious this was not the case, the vote 
of this member is not counted.

e. If a vote is not clear, means that not at least 

60% for 2 options
40 % for 3 options 

of all votes are clearly voting for one of the options, than the vote can either be 
repeated, of the MCF 'core team' can be called.

MCF 'core team' has to be elected in a vote of all MCF team members, this election 
has to be repeated every 6 months.

This team can make a final decision, if this should ever be necessary ( unlikely ).



2. Responsibilities / ranks / titles :

The following tasks are vital parts of the project IMHO, and we should have people 
being responsible for them :


- MCF specs creation and maintaining ( now : robux4 )

- main MCF library ( libmcf ) creation and maintaining ( now : robux4 )

- transor developement and creation ( now : robux4 )

- MCF windows parser/dshow filter development ( now : myFUN )

- MCF authoring tool development ( now : milkman.dan )

- Website creation and maintaining ( now : ? )

- Webforum administration ( now : ChristianHJW )

- Mailing lists administration ( now : ? )

- MCF Public Relations work ( includes news management on website soon )  ( now : 
ChristianHJW )


I assume we sould spread some of the tasks to other team members, as currently 
there is much too much on the shoulders of a few people only ( robux4 !!! ).

Anybody volunteering ??

As a matter of fact it will be essential, in order to keep motivation up, that the 
members taking over responsibility for a certain 'task' can work pretty freely there. In 
any case the other members can give their input, and if they don't agree with how its 
done they can force a decision of the team using the voting process described 
above.




Comments on both points are highly  appreciated

Christian


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf