1 |
Duncan wrote: |
2 |
> Ryan Hill <dirtyepic@g.o> posted |
3 |
> 20080603222620.71c89a1e@×××××××××××××××××.ca, excerpted below, on Tue, 03 |
4 |
> Jun 2008 22:26:20 -0600: |
5 |
> |
6 |
>> AFAIR nominating has always been open to anyone, dev and user alike. |
7 |
> |
8 |
> Which does make sense. Giving the community nomination power gives them |
9 |
> some input, while limiting the actual power and damage potential, since |
10 |
> they can't vote on their nominees, only devs do. As with any nominee, if |
11 |
> the devs don't like them, they simply vote for someone else. No harm |
12 |
> done unless the devs consent to it. |
13 |
> |
14 |
|
15 |
Agreed, but since there is a trend towards taking everything literally |
16 |
these days I do want to point out that this opens up a DoS attack - you |
17 |
could end up with a ballot 40 miles long if people use throwaway email |
18 |
addresses to make and second and accept nominations. |
19 |
|
20 |
Normally I'd just assume that if this were to happen common sense would |
21 |
prevail and these nominations would be excluded, but since there is a |
22 |
trend towards policy-trumps-sense perhaps the policy should be that |
23 |
anybody can nominate, but only devs can second a nomination? After all, |
24 |
if not even one dev supports a nomination what is the point of putting |
25 |
it on a ballot that only devs vote on? We could call the policy |
26 |
G:ACNBDMS (Gentoo: Anybody can nominate but devs must second) in tribute |
27 |
to another project where ability to quote policy is becoming more |
28 |
important than ability to add value... :) |
29 |
-- |
30 |
gentoo-dev@l.g.o mailing list |