| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
On 08/14/2011 03:19 PM, Roy Bamford wrote: |
| 5 |
> Team, |
| 6 |
> |
| 7 |
> I'll stir the pot a little. No flames please, after all, we are just |
| 8 |
> brainstorming, or to be PC having an idea shower. |
| 9 |
> |
| 10 |
Nobody is flaming :) |
| 11 |
|
| 12 |
> |
| 13 |
> On 2011.08.14 12:06, Markos Chandras wrote: |
| 14 |
>> Hi all, |
| 15 |
>> |
| 16 |
>> This is the first of the items I would like to discuss for the |
| 17 |
>> next Council agenda (or a later one). |
| 18 |
>> |
| 19 |
>> Some time ago, few people proposed to have Council appointed |
| 20 |
>> leaders for QA and DevRel. I like the idea because this way the |
| 21 |
>> Council can ensure that the team is active or either force some |
| 22 |
>> activity in case the current leader slacks big time. |
| 23 |
> |
| 24 |
> The concepts of appointing leaders and monitoring activity are not |
| 25 |
> linked. In my view a council appointed team lead is unlikely to do a |
| 26 |
> better job than one elected by the team. Choice of leader is |
| 27 |
> therefore no different to any other project. |
| 28 |
This should be the case, but what happens when the leader is inactive? |
| 29 |
Nobody is there to control the team or to force elections. Moreover, who |
| 30 |
is eligible to decide whether a lead is slacking or not. There is no |
| 31 |
definition for "slacker". With my proposal, the council will avoid all |
| 32 |
the chit-chatting ("are you active?", "yet I am", "no, it doesn't seem |
| 33 |
so" etc ) and bureaucracy that is required before someone takes action. |
| 34 |
> |
| 35 |
> Council may want to have some documented authority to take drastic |
| 36 |
> action in the case of slacking but that's separate again from |
| 37 |
> appointments and monitoring. Council would need to monitor to know |
| 38 |
> when drastic action was required. |
| 39 |
> |
| 40 |
> In short, --Routine_Appointments, ++Monitoring ++AuthortyToAct |
| 41 |
Well, what would that authority do? Report slacking teams? And then |
| 42 |
what? We still need some drastic action from the Council. |
| 43 |
|
| 44 |
> |
| 45 |
>> Furthermore, right now there is the potential problem for the |
| 46 |
>> leader to only allow new members that he likes so they can vote for |
| 47 |
>> him on next elections. |
| 48 |
> |
| 49 |
> We already have an appeal to council process that should be used. |
| 50 |
> I've formed the impression that these teams are as understaffed as |
| 51 |
> any other area of Gentoo, so no *competent* help should be refused. |
| 52 |
|
| 53 |
projects relations are not only horizontal but vertical as well. You |
| 54 |
can't possibly claim that the e.g virtualization@ project is as |
| 55 |
important as the QA team is. |
| 56 |
|
| 57 |
> How competent is judged needs to be documented by the teams - e.g. a |
| 58 |
> quiz and a practical under supervision before volunteers are turned |
| 59 |
> away. |
| 60 |
> |
| 61 |
>> Membership and voting actions should not be related in these teams. |
| 62 |
>> The leader will still have control over the new members but |
| 63 |
>> Council will do the voting (community will provide feedback ofc ) |
| 64 |
> |
| 65 |
> What do you mean by control ? |
| 66 |
Which members can join the project and which can't |
| 67 |
|
| 68 |
|
| 69 |
- -- |
| 70 |
Regards, |
| 71 |
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2 |
| 72 |
-----BEGIN PGP SIGNATURE----- |
| 73 |
Version: GnuPG v2.0.18 (GNU/Linux) |
| 74 |
|
| 75 |
iQIcBAEBCgAGBQJOR92IAAoJEPqDWhW0r/LCcKQP/1Nb1vJ0nFw+Jka47vnkcquK |
| 76 |
7ihA/WZJlQvLJCLY6Y3EFsXbkqynq9rvW0KbLYuIDpE2koZD+NKNp+qmzz0eib7a |
| 77 |
BaZK8AWPACpAY+OYJuL7+wolWmVMVvK6UBd8k3BIMW2UmBZBRgxCmk5gLrtZhd/i |
| 78 |
WjrvrJzrLTs2XqMlKVM4wzWnb/cSCeyeO8+Rl/pDHhePydIMei0uM22bgHQL7lVm |
| 79 |
och2eN2hEv6Q8op8ABemkxzmlSfGeZZRBcVEb09pRcjGGkQif5DcsDcDivJQkCrY |
| 80 |
e20zKCMZnBb1PsS87pPhq7D/pqYMBlq6yYwfP/z5m45/FdBQHRZj1xQYrypfbEKy |
| 81 |
RU3FydI7Ns2nmD385WzshZZfM1sgKEs1qZ+j5CTzTtVRLtJXBQfzNzCDv9rZPMft |
| 82 |
66TYG9iElRvfOi5uK9uxApFQaeDAiNBmDx4agELuvaUgjl+nqauCRFBfkbWZYMzK |
| 83 |
WcW7f6cFROzFqGrTdXldVDSp2plXJkcLNFxbgInicPybUIVP1+HSBjHx49WNm/6K |
| 84 |
RYbwIMMinP+hXNDQZqElhiYu1f45d8HlMkKQLQXg5U4OgPOB3Xa31Zgf9+Sa89AA |
| 85 |
KaphunMWV7YzCm88e8y+BoCzGCg8tIB02EVfYikXVHDuK3SoIUeEUTIPWuTFkgel |
| 86 |
hG2sU/Tc7EggzDTM9E+/ |
| 87 |
=qW0c |
| 88 |
-----END PGP SIGNATURE----- |
Archives