| 1 |
Summary for this topic. Again a list of voting propositions to be |
| 2 |
discussed during the meeting. |
| 3 |
|
| 4 |
- Unlike other projects the council does not need a lead. |
| 5 |
|
| 6 |
- The council needs a lead who will take charge of coordinating |
| 7 |
council actions and act as a speaker, secretary, chairman, etc.. (or |
| 8 |
will be responsible for finding somebody to execute these tasks), and |
| 9 |
will be the one to blame in case of them not being executed properly. |
| 10 |
|
| 11 |
- Same as above and the council lead gets an additional vote when |
| 12 |
needing to break ties. |
| 13 |
|
| 14 |
- The council needs a lead who will also act as community/distro |
| 15 |
leader. What exactly that could mean needs to be defined. |
| 16 |
|
| 17 |
Separate decision (which could depend on the result of the previous vote): |
| 18 |
|
| 19 |
- The council lead is elected by the newly elected members. The |
| 20 |
council members can decide to elect a new lead at any time (in case of |
| 21 |
away or slacking or else). |
| 22 |
|
| 23 |
- The council lead is elected by the developer community. How |
| 24 |
exactly? And how does the community replace the lead in case (s)he |
| 25 |
performs poorly or else? |
| 26 |
|
| 27 |
Denis. |
Archives