Restaffing
Differences between revisions 5 and 20 (spanning 15 versions)
|
Size: 4967
Comment:
|
← Revision 20 as of 2017-10-20 15:15:09 ⇥
Size: 58
Comment: Redirect to the new page on the Ubuntu Community Hub
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| = 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 done 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. 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 members of the particular governance body. The current list: * ~ubuntu-lococouncil: ~communitycouncil * ~ubuntu-irc-council: ~communitycouncil * ~forum-council: ~communitycouncil * ~ubuntu-membership-board-americas: ~communitycouncil * ~ubuntu-membership-board-asia-oceania: ~communitycouncil * ~ubuntu-membership-board-emea: ~communitycouncil * ~kubuntu-council: ~kubuntu-members * ~edubuntu-council: ~edubuntu-members * ~developer-membership-board: ~ubuntu-dev * ~techboard: ~ubuntu-dev * ~communitycouncil: ~ubuntumembers Sometimes you will have too many nominations for posts on your governance body, it might be good to mention your expectations in the announcement beforehand (5 open posts, ~10-12 nominees). In those cases you need to have your list of nominations short-listed. Short-listing is always done by the CC, and the CC needs the full list of nominations, preferrably annotated by the governance body looking for new staff. = 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 informatio 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``@`) }}} * 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. * [[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. == 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. 1. Prepare announce and requirements. (1 day) 1. ''Optional:'' Call for nominations. (2 weeks) 1. ''Optional:'' Shortlisting by CC. (1 week) 1. ''Optional:'' Call for nominations. (2 weeks) 1. ''Optional:'' Vote process. (2 weeks) 1. Announcement, necessary implementation. (1 day) = 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. 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 governance body by existing or former members is also ver valuable in bringing people up to speed. ---- CategoryCommunityCouncil |
#REFRESH 0 https://community.ubuntu.com/t/restaffing/890 |
CommunityCouncil/Restaffing (last edited 2017-10-20 15:15:09 by flexiondotorg)