1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 20-04-2010 17:40, Roy Bamford wrote: |
5 |
> On 2010.04.18 00:46, Denis Dupeyron wrote: |
6 |
>> During the last council meeting we discussed voting by email, see the |
7 |
>> log at [1]. What should we do about proxies if we make that happen? |
8 |
>> What's the impact on the slacker rule? |
9 |
>> |
10 |
>> [1] http://www.gentoo.org/proj/en/council/meeting-logs/20100308.txt |
11 |
> |
12 |
> Team, |
13 |
> |
14 |
> I have some strong views on voting by email. |
15 |
> |
16 |
> 1. Voting by email should be encouraged. This allows things to be |
17 |
> resolved on the mailing lists and never come to a council meeting. |
18 |
> It speeds the workflow and it therefore a good thing. |
19 |
> |
20 |
> 2. Voting by email in advance, on a topic to be *discussed* at a |
21 |
> meeting should not be permitted. In the event that the discussion |
22 |
> turns up something unexpected, there is no opportunity to vote in the |
23 |
> light of the new information. That further discussion is deemed to be |
24 |
> required, shows that not all the evidence is in and the council is not |
25 |
> ready to vote. |
26 |
|
27 |
I agree with Roy about the usefulness of voting by email and the |
28 |
"danger" of voting before meeting. |
29 |
|
30 |
> For the sake of clarity, if its just to announce a decision with no |
31 |
> opportunity for discussion, an email vote in advance of the |
32 |
> announcement is fine. |
33 |
|
34 |
I think this falls in the already exiting rule that nothing prevents the |
35 |
council of having impromptu meetings as deemed required and announcing |
36 |
decisions. This obviously doesn't apply to GLEP votes which have their |
37 |
own rules. |
38 |
|
39 |
> 3. email votes post discussion/meeting are fine. This allows GLEP39 to |
40 |
> be updated to remove both slacker marks and proxies which van only be a |
41 |
> good thing. |
42 |
|
43 |
I don't agree with Roy on this point as I think we still need some rules |
44 |
to ensure that the council members don't go MIA or that the body simply |
45 |
stops working. We can have more lenient rules, but they should still |
46 |
exist, IMHO. |
47 |
I do agree that dropping the ability of council members to send proxies |
48 |
to a meeting can avoid issues and is thus desirable. |
49 |
|
50 |
> Its perfectly possible for a member to serve properly on the council |
51 |
> and never show up to a meeting. With the span of time zones with the |
52 |
> current council, its already difficult for them to find a time to meet |
53 |
> and email voting would ease the pressure. |
54 |
|
55 |
I don't think it's desirable to have council members that don't show up |
56 |
to a single meeting or that hardly have direct talk with the other |
57 |
council members. If we ever get a council with people spread so far in |
58 |
the world that it isn't possible to find any schedule to host a meeting |
59 |
with everyone present, I would prefer the council to have rotating |
60 |
meetings to allow each member to attend a meeting from time to time. |
61 |
|
62 |
- -- |
63 |
Regards, |
64 |
|
65 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
66 |
Gentoo- forums / Userrel / Devrel / KDE / Elections |
67 |
-----BEGIN PGP SIGNATURE----- |
68 |
Version: GnuPG v2.0.15 (GNU/Linux) |
69 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
70 |
|
71 |
iQIcBAEBAgAGBQJLz46aAAoJEC8ZTXQF1qEPfjsP/2C07scMZmZ5hjg06x0KOaRn |
72 |
Hz6Sti8zqfX6ZEX6f7sUOTALm/EAdS8Yo5rxb9VZYrzdn07MVjzDQAIDFup1WMHV |
73 |
sRA/nAKEhD3aKThocAawndGIPpUgoAZxuFXTpYMuWDWlvtDbwA+0tKmH2muxFQlt |
74 |
m9b0qR82Ic+ddp/9KNgQzHJoDcgHSCeu0HXtCNv7Dq8JnxzB0jQ6mbdm5giTIjET |
75 |
9FClTKGuIfu12xtWCMWe6yVZPntMW20agn9OG0UV0GHDRSGRsKED+z/4DB5UCofo |
76 |
vKpIPEjeYiaehmLiLsmNnVpU3xA2hLqADDyJXoSK0+yon68ahWPxL2wH4ejun+Xe |
77 |
2cCh3qjawsdIqkVPj5pQnPM6WjZ2k3vwRMrgV3ELh8N6ufNoJOkPSgalIrzsgQDc |
78 |
dXZ3gpVXg1i+OkSCB06fBMQLmg5kF9r5wg0o/1kLzyjNTkzmAGEvdezqtfxyhFAf |
79 |
zrvmEY+NyTl5UN6guir3za9qLgS4Va2vKvwedv0YJhpwwHud5tuZTh79o2i7hz1M |
80 |
DI/IwbpEfuuXFjlmCb2npWJHkjkwJ25gkSMUPXLYMxEOpSWoLSkeQcZJwsvL4XKf |
81 |
WLIEUKcjxpFhzfssa/ONxNg7nlpK00qY40HPFl07NzUhmxJBFfMwm2rh9kNMIUu2 |
82 |
EVtBbBEkUQsEInCP9WDR |
83 |
=876+ |
84 |
-----END PGP SIGNATURE----- |