Community Council/Items/Election Process

This page is for review of propsed changes to the charter. The charter text that is published here is not approved.

Community Council Bylaws

Version 1.x

Last updated 2008-??-??

Council Constituencies

Status:proposal

approved on: not yet approved

According to the council charter (version 1.2) “Constituency” is “The group responsible for electing or appointing that particular representative as defined in the bylaws.”

Constituencies are defined as follows:

1. Product Development Representatives
   Category leads, project leads and co-leads of all OpenOffice.org projects (accepted and incubator) but not from the native-lang category or l10n project.
   (note: we might need to split this. None code contributing seats will be elected as suggested here. Code contributors might be elected by a list of active cvs committers)
2. Lang Representatives
   Category lead, project leads and co-leads from native-lang projects, plus project lead and co-leads of l10n project.
3. Community Contributor Representative
   All OpenOffice.org community members
4. Sun Staff Member
   Sun Microsystems, Inc and its management

Council Election process

Status:proposal

approved on: not yet approved

According to the council charter (version 1.2) the all Council Members (but the Sun Staff Member) will be elected using an open process that respects the principles of democracy and meritocracy.

The detailed process for electing the members and the constituency for each category will be written in the bylaws but has to respect these basic rules:

1. Each OpenOffice.org community member is eligible for election.
2. The call for candidates will be published at an online resource which is accessible for every community member.
3. Each community member is allowed to nominate candidates (including self-nomination).
4. Each candidate is encouraged to introduce herself.
5. Council members of the different categories will be elected by a corresponding constituency.

Process details

tbd