diff -uN constitution.txt constitution_new.txt

[Cornelius Weiss-4]

gbil:Desktop nelius$ diff -uN constitution.txt constitution_new.txt
--- constitution.txt    2007-12-17 22:17:34.000000000 +0100
+++ constitution_new.txt        2008-01-28 14:55:46.000000000 +0100
@@ -7,8 +7,8 @@
  1. Project administration
  The eGroupWare project has three equal and elected project  
administrators.
  The Administrators are the link between the several developers and  
they have administration rights on our development platforms (at the  
moment sf.net and the egroupware.org website).
-Administrators or a share of 20% the developers can call for a vote  
about new elections of the project administrators. This has to follow  
the decision making process outlined in the next paragraph.
-I case of elections, each developer elect three candidates  
individually. The three candidates with the most votes on their side  
are the new project administrators.
+Admins are elected for a term of 12 month. If for some reason the  
need for admin elections arrise within a term, the current  
administrators or a share of 20% the developers can call for a vote  
about new elections of the project administrators. This has to follow  
the decision making process outlined in the next paragraph.
+In case of elections, each developer elect three candidates  
individually. The three candidates with the most votes on their side  
are the new project administrators.

  2. Decision making process
  Regular decisions should include a consulting with the developers  
base via the mailinglist and all three administrators.
@@ -21,6 +21,7 @@
  If 20% of the active developers or one administrator is not  
satisfied with a decision, they can call for a vote by the active  
developers.
  Votes need to be formulated in writing and be published on the  
mailinglist at least one week in advance.
  They are considered accepted if 50% or more of the developers voting  
are agreeing.
+The project maintains a list of 'active developers' who are allowed  
to participate in votes. The details about becoming an 'active  
developer' are covered in the 'new members' document.

  3. Documentation of decisions and changes
  All decisions done by the administrators or conducted as vote of the  
developers have to be documented in public.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
eGroupWare-core mailing list
eGroupWare-core@...
https://lists.sourceforge.net/lists/listinfo/egroupware-core

[ralfbecker]

Hi Conny,

my origninal draft for the constitution had a limited term for the
admins. It was removed on the request of Lars!

Anyway I'm not against adding it - thought:
- it need to be done by a vote requiring a 2/3 majority for the change
of the constitution
- I think 12 month is to short, I suggest at least 2 years, as the
election campaign take for sure a certain amount of resources and activity

The question is also if a vote and maybe different administrators would
improve the situation of the project ... I'm not sure ...

If we come to a regular voting, please let's not do it in December to
Februar, when I'm always away from Germany. It's a real pain to stay up
to date via internet cafes.

Ralf

Cornelius Weiss schrieb:

> gbil:Desktop nelius$ diff -uN constitution.txt constitution_new.txt
> --- constitution.txt    2007-12-17 22:17:34.000000000 +0100
> +++ constitution_new.txt        2008-01-28 14:55:46.000000000 +0100
> @@ -7,8 +7,8 @@
>   1. Project administration
>   The eGroupWare project has three equal and elected project  
> administrators.
>   The Administrators are the link between the several developers and  
> they have administration rights on our development platforms (at the  
> moment sf.net and the egroupware.org website).
> -Administrators or a share of 20% the developers can call for a vote  
> about new elections of the project administrators. This has to follow  
> the decision making process outlined in the next paragraph.
> -I case of elections, each developer elect three candidates  
> individually. The three candidates with the most votes on their side  
> are the new project administrators.
> +Admins are elected for a term of 12 month. If for some reason the  
> need for admin elections arrise within a term, the current  
> administrators or a share of 20% the developers can call for a vote  
> about new elections of the project administrators. This has to follow  
> the decision making process outlined in the next paragraph.
> +In case of elections, each developer elect three candidates  
> individually. The three candidates with the most votes on their side  
> are the new project administrators.
>
>   2. Decision making process
>   Regular decisions should include a consulting with the developers  
> base via the mailinglist and all three administrators.
> @@ -21,6 +21,7 @@
>   If 20% of the active developers or one administrator is not  
> satisfied with a decision, they can call for a vote by the active  
> developers.
>   Votes need to be formulated in writing and be published on the  
> mailinglist at least one week in advance.
>   They are considered accepted if 50% or more of the developers voting  
> are agreeing.
> +The project maintains a list of 'active developers' who are allowed  
> to participate in votes. The details about becoming an 'active  
> developer' are covered in the 'new members' document.
>
>   3. Documentation of decisions and changes
>   All decisions done by the administrators or conducted as vote of the  
> developers have to be documented in public.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> eGroupWare-core mailing list
> eGroupWare-core@...
> https://lists.sourceforge.net/lists/listinfo/egroupware-core

--
Ralf Becker
eGroupWare Training & Support ==> http://www.egroupware-support.de
Outdoor Unlimited Training GmbH [www.outdoor-training.de]
Handelsregister HRB Kaiserslautern 3587
Geschäftsführer Birgit und Ralf Becker
Leibnizstr. 17, 67663 Kaiserslautern, Germany
Telefon [phone]


--
-- eGroupWare Training & Support ==> http://www.egroupware-support.deOutdoor
Unlimited Training GmbH [http://www.outdoor-training.de]Geschäftsführer:
Ralf und Birgit BeckerLeibnizstr. 1767663 Kaiserslautern</pre>



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
eGroupWare-core mailing list
eGroupWare-core@...
https://lists.sourceforge.net/lists/listinfo/egroupware-core