1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 2008.09.26 20:57, Ned Ludd wrote: |
5 |
> |
6 |
> On Fri, 2008-09-26 at 15:26 -0400, Mike Frysinger wrote: |
7 |
[snip] |
8 |
> > |
9 |
> > just make the replacement strategies the same. replacement for a |
10 |
> booted |
11 |
> > slacker is the same for someone who resigns council/Gentoo or is |
12 |
> kicked out. |
13 |
> > elections take time and are a hassle. selecting from the original |
14 |
> list is a |
15 |
> > lot simpler. |
16 |
> > -mike |
17 |
> |
18 |
> |
19 |
> I strongly disagree with this method. People opt to not run for the |
20 |
> council when they see what they expect to be a strong council. So if |
21 |
> you |
22 |
> see you have 8 pretty strong devs and 6 weak ones running. That's |
23 |
> good |
24 |
> enough sign to make you decline any nominations. As the people get |
25 |
> sick |
26 |
> etc this defaulting to the next inline can lead to results of the |
27 |
> council which could completely and radically destroy Gentoo. |
28 |
> |
29 |
|
30 |
Solar++ |
31 |
|
32 |
Allow the remaining council members to recruit any dev for the role, if |
33 |
the any dev agrees. Such recruits serve until the next election, when |
34 |
they can stand on their merits. |
35 |
|
36 |
It allows the council (if they wish) to appoint someone who complements |
37 |
the remaining members. It takes a little longer than the |
38 |
'inheirentence' method but I would expect it to produce a stronger |
39 |
council. |
40 |
|
41 |
- -- |
42 |
Regards, |
43 |
|
44 |
Roy Bamford |
45 |
(NeddySeagoon) a member of |
46 |
gentoo-ops |
47 |
forum-mods |
48 |
treecleaners |
49 |
trustees |
50 |
-----BEGIN PGP SIGNATURE----- |
51 |
Version: GnuPG v2.0.9 (GNU/Linux) |
52 |
|
53 |
iEYEARECAAYFAkjdRTQACgkQTE4/y7nJvauJxACglP5gfqPlOEQ5p5YpH6fHHUnB |
54 |
rDMAoInSUExtGCWmp9EKZjiM1DIB3Xiq |
55 |
=SJhY |
56 |
-----END PGP SIGNATURE----- |