| 1 |
Markos Chandras schrieb: |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> This is the first of the items I would like to discuss for the next |
| 5 |
> Council agenda (or a later one). |
| 6 |
> |
| 7 |
> Some time ago, few people proposed to have Council appointed leaders for |
| 8 |
> QA and DevRel. |
| 9 |
|
| 10 |
My first question: Why is your proposal restricted to QA and DevRel? |
| 11 |
|
| 12 |
> I like the idea because this way the Council can ensure |
| 13 |
> that the team is active or either force some activity in case the |
| 14 |
> current leader slacks big time. |
| 15 |
|
| 16 |
If there is noone active in a team, noone prevents other devs to join the team and vote themselves |
| 17 |
for the lead. So even if there is no activity, it should be no problem to get activity, if someone |
| 18 |
is interested to do the work. If the team is inactive and noone interested, the Council wont be able |
| 19 |
to create any activity either, since they cannot force anyone to do something. |
| 20 |
|
| 21 |
> Furthermore, right now there is the |
| 22 |
> potential problem for the leader to only allow new members that he likes |
| 23 |
> so they can vote for him on next elections. Membership and voting |
| 24 |
> actions should not be related in these teams. |
| 25 |
|
| 26 |
How is this specific to those 2 projects? Other projects do work the same way, so if you argument |
| 27 |
this way, you should extend your proposal to all projects, not just QA and DevRel. |
Archives