Hi Sophie,
sophie schrieb:
André Schnabel wrote:
...
> So .. my proposal:
> - leave the structure of the council as it is (1 CCR, 2 NL, 5
Project Leads, 1 Sun)
> - Structure is not defined by "who is eligible" but "who can vote"
> - every project member is eligible (where project member is
"Observer" - we may restrict this to "developer in one project")
> - elections willl mostly stay the same with following modifications:
> - call for candidates needs to be on a public list (discuss@ for
CCR, [EMAIL PROTECTED] for NL, dev@ for Project Leads)
> - anyone who is eligible can nominate herself and should introduce
herself (and why she thinks she should sit at the council) on the
above named list
> - CCR is elected by all Community members,
> - NLs are elected by Native Lang leads (+NL cathegory lead),
> - PLs are elected by Project Leads (accepted + incubator + resp.
cathegory leads - native lang)
> - other details about voting scheme are written in the bylaws, not
in the charter (so remove statements about quorum from current charter
or number of candidates)
I don't see any difference if we leave the structure of the Council as
it is currently or do you mean that roles from developers to leads are
eligible?
I'd suggest that even observers are eligible. This is from my
perspective as long term native-lang project member and my work at the
QA project. For those projects the member status (observer, developer,
content developer, owner ...) often does not reflect who is actively
contributing.
But I'd like to see more input here from "coding project" members.
In that last case, the structure is changed?
I don't think, that the structure (where structure means "what groups of
the community are represented in the Council) really needs a change. IMO
the current restricted number of eligible persons (who are willing to be
elected) lead to a more or less "fixed" team of coucil members. (Not to
criticise the council members - I just think, that we need more frequent
changes.)
That leave also a large part of the contributors out of the scheme
(I'm thinking about QA members or Documentation members for example),
but it will be more open than at the moment.
As said - there for I'd like to see that all community members are
eligible :)
Hope, this helps,
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
