| 1 |
On Sat, 2007-07-21 at 13:31 +0100, Roy Bamford wrote: |
| 2 |
> That's the beginnings of a good election manifesto. All the candidates |
| 3 |
> need to explain, if they are elected :- |
| 4 |
> |
| 5 |
> 1. What they will do |
| 6 |
> 2. Why they will do it |
| 7 |
> 3. How they will do it |
| 8 |
> 4. Timescales for their plans. |
| 9 |
|
| 10 |
5. Experience doing similar things in other arenas |
| 11 |
6. Why they think they're qualified for the position |
| 12 |
7. How they plan on adding the Council work into their normal Gentoo |
| 13 |
work load |
| 14 |
8. How much time they have to dedicate to Council tasks |
| 15 |
|
| 16 |
These last two are probably some of the most important to me, since I |
| 17 |
have seen first-hand how much time the Council can take. Here's a |
| 18 |
glimpse, for the rest of you... When the Council was working on the CoC, |
| 19 |
I spent in excess of 50 hours in one week working solely on the CoC. |
| 20 |
This means I put my actual paying job on the back burner for the Council |
| 21 |
because I pretty much had to do so. The Council is *not* only a once a |
| 22 |
month job. You're a Council member every hour of every day for a year. |
| 23 |
|
| 24 |
> This information will allow the electorate to choose a team with |
| 25 |
> similar aims, so we get a cohesive council, not a collection of |
| 26 |
> individuals trying to take Gentoo in different directions. |
| 27 |
|
| 28 |
I know that I will likely be choosing people of a like mind to myself. |
| 29 |
I'll also probably be picking people the *least* likely to be pushing |
| 30 |
for a ton of changes, simply because I also don't think we need 7 people |
| 31 |
pushing in 7 directions only trying to get *their* ideas enacted. |
| 32 |
|
| 33 |
> Any candidate unwilling to prepare such a manifesto should withdraw now |
| 34 |
> as they clearly don't have the time or interest to take an active seat |
| 35 |
> on the council. |
| 36 |
|
| 37 |
Agreed. |
| 38 |
|
| 39 |
> Like it or not, the council is more of a social/political body than a |
| 40 |
> development body. |
| 41 |
|
| 42 |
This is really true. While the Council is the main technical body, we |
| 43 |
tend to make technical decisions very quickly and without controversy. |
| 44 |
Social/political issues are almost always very long-running and tend to |
| 45 |
take up more of our time. If I were to guess, I would say that 90% of |
| 46 |
what we do is technical, but the 10% that is non-technical takes up 90% |
| 47 |
of our time. |
| 48 |
|
| 49 |
-- |
| 50 |
Chris Gianelloni |
| 51 |
Release Engineering Strategic Lead |
| 52 |
Alpha/AMD64/x86 Architecture Teams |
| 53 |
Games Developer/Council Member/Foundation Trustee |
| 54 |
Gentoo Foundation |
Archives