Restaffing
|
Size: 3447
Comment:
|
Size: 9553
Comment: added paragraph on confirmation polls
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from CommunityCouncil/RestaffingProposal | |
| Line 4: | Line 5: |
| Every Ubuntu Council or Board has a specific term length for their members defined. The only exception is Mark Shuttleworth's seat (aka SABDFL) on the CommunityCouncil and TechnicalBoard. So whenever the term length of members of a board ends, restaffing the board is necessary. There are other cases where members might decide to step done from their post because of lack of time or other obligations. | Every Ubuntu Governance Body (Council or Board) has a specific term length for their members defined. The only exception is Mark Shuttleworth's seat (aka SABDFL) on the CommunityCouncil and TechnicalBoard. So whenever the term length of members of a governance body ends, restaffing is necessary. There are other cases where members might decide to step down from their post because of lack of time or other obligations. |
| Line 6: | Line 7: |
| At each UDS the list of boards and councils is checked for expiries. | At each UDS the list of governance bodies is checked for expiries in a session of the Community track. |
| Line 8: | Line 9: |
| The re-staffing can happen in form of an election or an appointment. While the Community Council and Technical Board reserve the right to appoint if it's necessary, in the majority of cases an election will be the preferred solution. This will happen, when there is a clearly governed subteam of Ubuntu members who can vote the new board or council members. For example: | == Timeline == |
| Line 10: | Line 11: |
| * ~ubuntu-dev would vote new ~techboard members * ~ubuntu-dev would vote new ~developer-membership-board members * ~ubuntumembers would vote new ~communitycouncil members * etc. |
Please note that in some cases no election happens and in other cases short-listing might not be necessary. The durations mentioned below have worked well in the past. |
| Line 15: | Line 13: |
| An example where it's not quite clear who would vote is the LoCo Council. | 1. Prepare announce and requirements. (1 day) 1. ''Optional:'' Call for nominations. (2 weeks) 1. ''Optional:'' Shortlisting by CC. (1 week) 1. ''Optional:'' Vote process. (2 weeks) 1. Announcement, necessary implementation. (1 day) == Appointments and Polls == Positions on leadership boards are appointed by the governance body that is delegating authority to them. In many, if not most cases, that delegation will be supported by a poll of relevant members of the community. While the Community Council and Technical Board reserve the right to make direct appointments without a supporting poll if necessary, in the majority of cases a poll will be the preferred solution. When a poll is conducted, it will usually not involve the entire Ubuntu community. We try to arrange the community structure in such a way that there is a group of people (usually identified by a Launchpad team) that are in some way more closely associated with that particular aspect of the project. Ideally, those people are also members of Ubuntu, but that will not always be the case. Essentially, they are the group that will be most directly affected by the appointment, and we generally wish to poll them to establish their confidence in the appointments being made. == Calls for Nominations == In general, we prefer to conduct a call for nominations when positions of responsibility are open. The process for generating the list of nominees for a seat on a Council is as follows: 1. The existing Council will usually issue that call for nominations for additional members. (If applicable you might want to use Launchpad's "Contact this team's members" feature for reaching out among the voting team.) 1. The Council will verify that nominated persons are interested and willing to serve. 1. The Council or Board should forward ALL nominations to the Community Council, identifying those who are willing to serve, together with their commentary in support of or against particular nominees. The Council should not shortlist, or filter, the nominees. 1. The Community Council will then publish the final list of candidates for the seat(s). If a poll is called for, the Council will setup the poll, sometimes with the help of a member of the Community Council. The CC will determine the appropriate group to be polled. Currently, it is practice to poll the following teams for appointments to specific leadership boards or councils: || '''Governance Body''' || '''selected by members of this team''' || || [[LoCoCouncil|LoCo Council]] ([[https://launchpad.net/~ubuntu-lococouncil|~ubuntu-lococouncil]]) || [[CommunityCouncil|Community Council]] ([[https://launchpad.net/~communitycouncil|~communitycouncil]]) || || [[IRC/IrcCouncil|IRC Council]] ([[https://launchpad.net/~ubuntu-irc-council|~ubuntu-irc-council]]) || [[IRC/Membership|Ubuntu IRC Members]] ([[https://launchpad.net/~ubuntu-irc-members|~ubuntu-irc-members]]) || || [[ForumCouncil|Forums Council]] ([[https://launchpad.net/~forum-council|~forum-council]]) || [[CommunityCouncil|Community Council]] ([[https://launchpad.net/~communitycouncil|~communitycouncil]]) || || [[Membership/RegionalBoards/Americas|Regional Membership Board Americas]] ([[https://launchpad.net/~ubuntu-membership-board-americas|~ubuntu-membership-board-americas]]) || [[CommunityCouncil|Community Council]] ([[https://launchpad.net/~communitycouncil|~communitycouncil]]) || || [[Membership/RegionalBoards/AsiaOceania|Regional Membership Board Asia/Oceania]] ([[https://launchpad.net/~ubuntu-membership-board-asia-oceania|~ubuntu-membership-board-asia-oceania]]) || [[CommunityCouncil|Community Council]] ([[https://launchpad.net/~communitycouncil|~communitycouncil]]) || || [[Membership/RegionalBoards/EMEA|Regional Membership Board EMEA]] ([[https://launchpad.net/~ubuntu-membership-board-emea|~ubuntu-membership-board-emea]]) || [[CommunityCouncil|Community Council]] ([[https://launchpad.net/~communitycouncil|~communitycouncil]]) || || [[Kubuntu/Meetings|Kubuntu Council]] ([[https://launchpad.net/~kubuntu-council|~kubuntu-council]]) || [[Kubuntu/Meetings|Kubuntu]] [[Membership|Members]] ([[https://launchpad.net/~kubuntu-members|~kubuntu-members]]) || || [[Edubuntu/Council|Edubuntu Council]] ([[https://launchpad.net/~edubuntu-council|~edubuntu-council]]) || [[Edubuntu]] [[Membership|Members]] ([[https://launchpad.net/~edubuntu-members|~edubuntu-members]]) || || [[DeveloperMembershipBoard|Developer Membership Board]] ([[https://launchpad.net/~developer-membership-board|~developer-membership-board]]) || [[UbuntuDevelopers|Ubuntu Developers]] ([[https://launchpad.net/~ubuntu-dev|~ubuntu-dev]]) || || [[TechnicalBoard|Technical Board]] ([[https://launchpad.net/~techboard|~techboard]]) || [[UbuntuDevelopers|Ubuntu Developers]] ([[https://launchpad.net/~ubuntu-dev|~ubuntu-dev]]) || || [[CommunityCouncil|Community Council]] ([[https://launchpad.net/~communitycouncil|~communitycouncil]]) || [[Membership|Ubuntu Members]] ([[https://launchpad.net/~ubuntumembers|~ubuntumembers]]) || = Confirmation Polls = In the unlikely event that the number of candidates is exactly the same as the number of seats in a Council, a confirmation poll should be run. Each candidate will run individually in "yes-no" poll. If the majority of voters approve that candidate, they will be confirmed as a member of the Council. In order to set up a confirmation poll, you should use Launchpad poll feature available from your team page. |
| Line 19: | Line 57: |
| If you coordinate the restaffing of a board or council, you might want to give the nomination part special thought. Make sure you make the list of responsibilities and the type of personalities you are looking for are quite clear when announcing the nomination period. Self-nominations, nominations by others, both? Which information do you want nominees to include? Will you need to short-list the number of nominees (if you're having an election)? Please also make sure that you leave at least 1-2 weeks for that nomination period and make sure the relevant people know about it. | * the team should have established guidelines for the necessary qualifications for its members, and the person running the election should provide these to help with nomination * the normal nomination period is 2 weeks but can be adjusted if circumstances warrant it * nominations should generally be open to anyone with the necessary qualifications (as established by the team), though the team may choose to do differently (e.g. the CC) |
| Line 23: | Line 63: |
| You might want to ask the (probably short-listed) nominees to write something about their ideas and plans on their wiki pages, so voters will be better informed about who they vote. | It is important that you ask nominees to write something about their ideas and plans on their wiki pages, so voters will be better informed about who they vote. Without this information voters will just look at a list of names that don't say anything. This template might be useful information to include on their personal wiki page. {{{ == General == * Name: * Contact details: === Key Achievements === ... == Vision == <vision for the leadership role> == Testimonials == * ... (please don't forget to sign with your `@``SIG``@`) == Comments == * ... (please don't forget to sign with your `@``SIG``@`) }}} The announcement should go to the most appropriate team mailing list, so you get the attention of everybody who takes an interest in that particular part of the community. For additional effect (you might want broader feedback), [[PlanetUbuntu|blog]] about the nomination/election, get the announce on the [[Fridge]] and put a link to the announcement in the topic of the team channel. |
| Line 28: | Line 88: |
| * [[http://www.cs.cornell.edu/andru/civs.html|CIVS]] makes use of the [[http://en.wikipedia.org/wiki/Condorcet_method|Concordet method]] which can be more suitable. | * [[http://www.cs.cornell.edu/andru/civs.html|CIVS]] makes use of the [[http://en.wikipedia.org/wiki/Condorcet_method|Concordet method]] which can be more suitable when you are selecting m-of-n candidates, for example if you have 5 candidates for 3 places. The voting algorithm used is the [[http://en.wikipedia.org/wiki/Cloneproof_Schwartz_Sequential_Dropping|Shulze method]]. In the case of a tie, the CC will privately discuss and agree on which candidate wins. |
| Line 32: | Line 92: |
| Make sure the new faces on the board or council are announced and maybe even ask them to introduce themselves. DeveloperCommunication has good tips how and where to announce and why. Make sure you thank everybody who participated in the election or nomination period. | Make sure the new faces on the governance body are announced and maybe even ask them to introduce themselves. DeveloperCommunication has good tips how and where to announce and why. Make sure you thank everybody who participated in the election or nomination period. |
| Line 34: | Line 94: |
| Aftwards be sure to update Launchpad, the wiki pages, ubuntu.com and whatever else is necessary. Also make sure they get on the [[https://lists.ubuntu.com/mailman/listinfo/team-council-members|team-council-members mailing list]]. An introduction to the council or board by existing or former members is also ver valuable in bringing people up to speed. | Please update Launchpad, the wiki pages, ubuntu.com and whatever else is necessary. Also make sure they subscribe to ubuntu-council-teams@lists.launchpad.net. An introduction to the governance body by existing or former members is also very valuable in bringing people up to speed. |
Restaffing generally
Every Ubuntu Governance Body (Council or Board) has a specific term length for their members defined. The only exception is Mark Shuttleworth's seat (aka SABDFL) on the CommunityCouncil and TechnicalBoard. So whenever the term length of members of a governance body ends, restaffing is necessary. There are other cases where members might decide to step down from their post because of lack of time or other obligations.
At each UDS the list of governance bodies is checked for expiries in a session of the Community track.
Timeline
Please note that in some cases no election happens and in other cases short-listing might not be necessary. The durations mentioned below have worked well in the past.
- Prepare announce and requirements. (1 day)
Optional: Call for nominations. (2 weeks)
Optional: Shortlisting by CC. (1 week)
Optional: Vote process. (2 weeks)
- Announcement, necessary implementation. (1 day)
Appointments and Polls
Positions on leadership boards are appointed by the governance body that is delegating authority to them. In many, if not most cases, that delegation will be supported by a poll of relevant members of the community. While the Community Council and Technical Board reserve the right to make direct appointments without a supporting poll if necessary, in the majority of cases a poll will be the preferred solution.
When a poll is conducted, it will usually not involve the entire Ubuntu community. We try to arrange the community structure in such a way that there is a group of people (usually identified by a Launchpad team) that are in some way more closely associated with that particular aspect of the project. Ideally, those people are also members of Ubuntu, but that will not always be the case. Essentially, they are the group that will be most directly affected by the appointment, and we generally wish to poll them to establish their confidence in the appointments being made.
Calls for Nominations
In general, we prefer to conduct a call for nominations when positions of responsibility are open. The process for generating the list of nominees for a seat on a Council is as follows:
- The existing Council will usually issue that call for nominations for additional members. (If applicable you might want to use Launchpad's "Contact this team's members" feature for reaching out among the voting team.)
- The Council will verify that nominated persons are interested and willing to serve.
- The Council or Board should forward ALL nominations to the Community Council, identifying those who are willing to serve, together with their commentary in support of or against particular nominees. The Council should not shortlist, or filter, the nominees.
- The Community Council will then publish the final list of candidates for the seat(s). If a poll is called for, the Council will setup the poll, sometimes with the help of a member of the Community Council. The CC will determine the appropriate group to be polled.
Currently, it is practice to poll the following teams for appointments to specific leadership boards or councils:
Governance Body |
selected by members of this team |
Regional Membership Board Americas (~ubuntu-membership-board-americas) |
|
Regional Membership Board Asia/Oceania (~ubuntu-membership-board-asia-oceania) |
|
Regional Membership Board EMEA (~ubuntu-membership-board-emea) |
|
Confirmation Polls
In the unlikely event that the number of candidates is exactly the same as the number of seats in a Council, a confirmation poll should be run. Each candidate will run individually in "yes-no" poll. If the majority of voters approve that candidate, they will be confirmed as a member of the Council.
In order to set up a confirmation poll, you should use Launchpad poll feature available from your team page.
Announcing and planning an election
- the team should have established guidelines for the necessary qualifications for its members, and the person running the election should provide these to help with nomination
- the normal nomination period is 2 weeks but can be adjusted if circumstances warrant it
- nominations should generally be open to anyone with the necessary qualifications (as established by the team), though the team may choose to do differently (e.g. the CC)
In the case of an election you will have to set up the poll and announce it once you have a suitable number of nominees. Be clear about who will be allowed to vote and set up the poll.
It is important that you ask nominees to write something about their ideas and plans on their wiki pages, so voters will be better informed about who they vote. Without this information voters will just look at a list of names that don't say anything.
This template might be useful information to include on their personal wiki page.
== General == * Name: * Contact details: === Key Achievements === ... == Vision == <vision for the leadership role> == Testimonials == * ... (please don't forget to sign with your `@``SIG``@`) == Comments == * ... (please don't forget to sign with your `@``SIG``@`)
The announcement should go to the most appropriate team mailing list, so you get the attention of everybody who takes an interest in that particular part of the community. For additional effect (you might want broader feedback), blog about the nomination/election, get the announce on the Fridge and put a link to the announcement in the topic of the team channel.
- Launchpad votes are pretty straightforward, but a bit limited in its setup, either you
set up one poll for the whole election and see who gets the top <x> of <y> votes (5 of 12, when you have 12 nominees and 5 seats) or
- set up one poll per person and see who gets the most "Yes minus No" votes.
CIVS makes use of the Concordet method which can be more suitable when you are selecting m-of-n candidates, for example if you have 5 candidates for 3 places. The voting algorithm used is the Shulze method. In the case of a tie, the CC will privately discuss and agree on which candidate wins.
The outcome
Make sure the new faces on the governance body are announced and maybe even ask them to introduce themselves. DeveloperCommunication has good tips how and where to announce and why. Make sure you thank everybody who participated in the election or nomination period.
Please update Launchpad, the wiki pages, ubuntu.com and whatever else is necessary. Also make sure they subscribe to ubuntu-council-teams@lists.launchpad.net. An introduction to the governance body by existing or former members is also very valuable in bringing people up to speed.
CommunityCouncil/Restaffing (last edited 2017-10-20 15:15:09 by flexiondotorg)