Difference between revisions of "Zedling Council"
From Zedwiki
m (→The Council Code of Conduct: Minor change to better support section linking) |
m (→The Council Code of Conduct) |
||
| Line 60: | Line 60: | ||
== The Council Code of Conduct == | == The Council Code of Conduct == | ||
| − | === Expectations | + | === Expectations and Responsibilities of the Council === |
All Council Members are expected to abide by these codes. The codes are enforced by the Host of the meeting, and the Council itself. If any of these codes are violated during a meeting, the Host is obligated to warn the violating member or issue a strike against them (in exception of codes with mandatory pre-strike warnings) The Council Code of Conduct is enforced with a Two-Strike Policy. Once a member receives their second strike, they will be removed from the Council. The Council may vote to remove a member's strike if they wish to forgive/pardon a member's actions (if the member has shown remorse for their violation, and indicates they will not violate the Code of Conduct again) or if the Council disagrees with the Host's decision to issue the strike. The recipient of the strike may raise a topic during the next meeting to apologize and ask the Council to vote if they wish to appeal the strike. [Created 2016-01-02] | All Council Members are expected to abide by these codes. The codes are enforced by the Host of the meeting, and the Council itself. If any of these codes are violated during a meeting, the Host is obligated to warn the violating member or issue a strike against them (in exception of codes with mandatory pre-strike warnings) The Council Code of Conduct is enforced with a Two-Strike Policy. Once a member receives their second strike, they will be removed from the Council. The Council may vote to remove a member's strike if they wish to forgive/pardon a member's actions (if the member has shown remorse for their violation, and indicates they will not violate the Code of Conduct again) or if the Council disagrees with the Host's decision to issue the strike. The recipient of the strike may raise a topic during the next meeting to apologize and ask the Council to vote if they wish to appeal the strike. [Created 2016-01-02] | ||
| − | === Expectations | + | === Expectations and Responsibilities of the Host === |
The Host is responsible for maintaining order during the meeting, and is expected to use their judgement and work with the rest of the Council to enforce the Code of Conduct. The Host is responsible for issuing warnings and/or strikes if a member violates one of the [[Zedling_Council#Code_of_Conduct|Codes of Conduct]] . [Created 2016-01-02] | The Host is responsible for maintaining order during the meeting, and is expected to use their judgement and work with the rest of the Council to enforce the Code of Conduct. The Host is responsible for issuing warnings and/or strikes if a member violates one of the [[Zedling_Council#Code_of_Conduct|Codes of Conduct]] . [Created 2016-01-02] | ||
| − | === Expectations | + | === Expectations and Responsibilities of the Scribe === |
The Scribe volunteers at the beginning of a meeting. They are responsible for documenting the meeting, discussions held and decisions made. This is for the benefit of absent council members and for future reference. These 'notes' also include the attendance of the meeting: council members are recorded for the purposes of maintaining accurate attendance strikes; guest attendance is also included to keep a record of non-members who are regularly interested in council affairs. Once the notes are completed, the scribe is responsible for adding these to the appropriate wiki page and making a forum thread for the next meeting's agenda (see regulation 2) | The Scribe volunteers at the beginning of a meeting. They are responsible for documenting the meeting, discussions held and decisions made. This is for the benefit of absent council members and for future reference. These 'notes' also include the attendance of the meeting: council members are recorded for the purposes of maintaining accurate attendance strikes; guest attendance is also included to keep a record of non-members who are regularly interested in council affairs. Once the notes are completed, the scribe is responsible for adding these to the appropriate wiki page and making a forum thread for the next meeting's agenda (see regulation 2) | ||
Revision as of 12:07, 20 May 2018
The council meets bi-weekly to discuss matters important to the community; these may include proposed events, modifying or creating the infrastructure (The Market, Nether Hub, railways, funds etc.), or hassling Zed to change how the server is run. Council members are voted in by existing members, though there is currently a maximum limit of 20 members of the council at any one time. Places may open up as existing members become inactive.
Next meeting: 2018-05-19 8PM BST, hosted by ABParadigm
Meeting Agenda: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=2861
Contents
Current members
[Strikes last updated from 2018-05-05]
- Zedwick [From 2014-09-20]
- LadyBountiful [From 2014-09-20]
- SneakySkeleton [From 2014-09-20]
- Dax23333 [From 2014-10-04]
- Forseth [From 2015-03-21] [Attendance Strikes: 1] [1]
- HOMINIX [From 2015-07-04] [Attendance Strikes: 2] [2] [1]
- Memery [From 2016-04-09]
- ACERPROSPY [From 2016-04-23] [Attendance Strikes: 1] [1]
- _Swayed_ [From 2016-09-24] [Attendance Strikes: 1] [3]
- Aravero [From 2016-11-19]
- Spectatre [From 2017-02-11]
- ABParadigm [From 2017-05-07]
- EliasRipley [From 2017-11-18]
- KhasOrn [From 2018-01-27] [Attendance Strikes: 1] [1]
- SooprJ [From 2018-02-10]
- tim1996 [From 2018-03-10] [Attendance Strikes: 1] [1]
- EarthCow [From 2018-05-05]
The Council Regulations
- Council Meetings are hosted by the chairperson, who is responsible for selecting the location and organising the schedule for the meeting. A new chairperson is elected each meeting. [Referenced 2014-04-14]
- The scribe for each meeting will post a pre-meeting agenda topic for the following meeting to the forums which would decide planned discussions, non-member Queries and any other business for the meeting. The forum post should include a link to notes from the previous meeting[Created 2014-12-13] [Amended 2017-10-21] [4]
- The Council may only have a maximum of 20 members at any given time. [Created 2014-12-27]
- Only 1 Council Member may be elected per meeting. [Confirmed 2015-11-07]
- Potential nominees must be nominated by at least two council members. They must also hold the highest votes, with a minimum of three, to win the candidacy. [Updated 2015-11-07] [Amended 2017-10-21] [4]
- Only current members of The Council may vote on topics, including elections, unless otherwise allowed by the council [Confirmed 2015-11-07]
- All Zedlings may attend council meetings but are asked not to speak unless allowed by The Council [Confirmed 2015-11-07]
- Attendees are encouraged not to wear armour during meetings, with the exception of boots and chainmail. This rule is not enforced, only encouraged. [Created 2014-12-13]
- Any resignations of a council member from The Council will not come into effect until the meeting after the meeting it was announced in. If a resignation is given on the forum or otherwise between meetings, the council must hear of it in a meeting for it to be officially recognised and then will only take effect at the following meeting's end. [Created 2015-07-18]
- Absence will be marked if a member fails to turn up before the end of a meeting, there is no cut-off point during a meeting. [Created 2015-08-29]
- If a council member does not attend a council meeting, without prior notice and apology, they will receive an attendance ‘strike’. If a council member has a total of three strikes in a row at the beginning of a meeting, they are considered in-active. This means they will be removed the meeting after their third strike. [Created 2014-12-27] [Referenced 2015-01-10] [Amended 2016-05-21][5][Amended again 2016-05-21][6]
- Co-mayors may be appointed between council meetings if the mayor creates a new forum topic announcing who they would like to appoint and why. The announcement must also then be made at the next council meeting, council members are allowed to veto with an explanation. [Created 2015-11-21]
- Council warp Mayoral voting system - full detail available on the Warp Mayor Page [Created 2015-12-20] [Amended 2017-07-29] [7]
- Warp towns will be reviewed at each council meeting to check that the mayors are active, and hear new of their progress. Temporary or replacement mayors may be appointed if mayors become inactive [Created 2015-12-20] [Effectively rescinded 2017-11-18] [8]
- If attendance is not recorded for a meeting, any absence from that meeting is excused, and no attendance strikes will be added. [Created 2016-01-02]
- If no Pre-Meeting Agenda thread exists, Council Members should post topic ideas, discuss upcoming meetings, or apologise in advance for an absence in the Zedling Council thread [Created 2016-01-02]
- All nominations and votes to elect a new council member are to be done via private message to the host of the meeting, this aims to prevent peer pressure and create an honest vote. [Created 2016-07-30][5] [Amended 2017-10-21][4]
- Banned players are to be immediately removed from the council members list upon ban. If the player was banned, but later the ban was to be found illegitimate, the player will be welcomed back by the Guardians and their council spot will be reinstated.[9]
- Players must be at least Zedling in order to be nominated to be a member of the council.
- When electing a new member, should voting result in a tie, the player with the highest meeting attendance for the last four meetings wins. If these are the same then the host must find an additional way to resolve the tie. [Amended 2017-10-21][4]
- An apology must be stated clearly on the forums in general discourse. [Created 2017-01-14] [10]
- Council Members retain their current strikes, even after apologising. The only way to remove strikes is to attend meetings. [Created 2017-01-14] [10]
- Council Members are allowed to make an advanced apology, for up to three meetings in a row, if they know they will be inactive. This is referred to as a ‘bulk apology’. [Created 2017-01-14] [10]
- If the council member requires more time after the ‘bulk apology’ period has ended; they must apologise before each subsequent meeting they miss. [Created 2017-01-14] [10]
- Only players with one strike or less are able to make a ‘bulk apology’. [Created 2017-01-14] [10]
- The council is able to remove a member (if a majority vote is passed) if that member has not attended 6 consecutive meetings, regardless of apologies. [Created 2017-01-14] [10]
- The Council may initiate a "vote" to come to a solid decision on a topic. [Created 2017-02-25] [11]
- The Council may take a "poll" to get an opinion on a topic. This is distinct from a "vote" as the outcome is not a concrete decision, but just providing an opinion. Results from polls should be given in a number of YES votes and number of NO votes, eg. 3-4. Polls can be between a range of options, not just yes/no answers. [Created 2017-02-25] [11]
- When a host has received at least two nominations for a player to join the council, they must gain that player's permission via private message, prior to naming them at the voting stage. If the player declines or is not present at the time of the meeting to give permission, their nomination is not to be included on the ballot. [Created 2017-10-21] [4]
- Meetings have a maximum of 90 minutes for topic discussion; 30 minutes for any one topic. Topics posted in the pre-meeting agenda take priority, with any non-posted topics being addressed if there is time remaining in the meeting. After the 90 minutes has elapsed the meeting moves to announcements and end-of-meeting business [Created 2017-12-30] [12]
The Council Code of Conduct
Expectations and Responsibilities of the Council
All Council Members are expected to abide by these codes. The codes are enforced by the Host of the meeting, and the Council itself. If any of these codes are violated during a meeting, the Host is obligated to warn the violating member or issue a strike against them (in exception of codes with mandatory pre-strike warnings) The Council Code of Conduct is enforced with a Two-Strike Policy. Once a member receives their second strike, they will be removed from the Council. The Council may vote to remove a member's strike if they wish to forgive/pardon a member's actions (if the member has shown remorse for their violation, and indicates they will not violate the Code of Conduct again) or if the Council disagrees with the Host's decision to issue the strike. The recipient of the strike may raise a topic during the next meeting to apologize and ask the Council to vote if they wish to appeal the strike. [Created 2016-01-02]
Expectations and Responsibilities of the Host
The Host is responsible for maintaining order during the meeting, and is expected to use their judgement and work with the rest of the Council to enforce the Code of Conduct. The Host is responsible for issuing warnings and/or strikes if a member violates one of the Codes of Conduct . [Created 2016-01-02]
Expectations and Responsibilities of the Scribe
The Scribe volunteers at the beginning of a meeting. They are responsible for documenting the meeting, discussions held and decisions made. This is for the benefit of absent council members and for future reference. These 'notes' also include the attendance of the meeting: council members are recorded for the purposes of maintaining accurate attendance strikes; guest attendance is also included to keep a record of non-members who are regularly interested in council affairs. Once the notes are completed, the scribe is responsible for adding these to the appropriate wiki page and making a forum thread for the next meeting's agenda (see regulation 2)
Code of Conduct
- All Council members shall follow all server rules, and are generally expected to act as model community members. Council members shall discuss topics in a respectful and civil manner. Any targeted insults or negative comments toward other members or guests will not be tolerated. [Created 2016-01-02]
- Council members are expected to focus on the topics at hand, and are encouraged to guide members back on topic if the conversation starts to wander or to move things along if the conversation starts to stagnate. [Created 2016-01-02]
- Disruptive or annoying behaviour such as making multiple entities, (firing several arrows or constantly dropping items) annoying other members, or generally being disruptive during the meeting is highly discouraged. The Host must issue a warning to the disruptive member first, but if this behaviour is continued, a strike may be issued by the Host. [Created 2016-01-02]
Meeting Notes
- 2018-05-19: Zedling Council Meeting 2018-05-19[13]
- 2018-05-05: Zedling Council Meeting 2018-05-05[1]
- 2018-04-21: Zedling Council Meeting 2018-04-21[2]
- 2018-04-07: Zedling Council Meeting 2018-04-07[3]
- 2018-03-24: Zedling Council Meeting 2018-03-24[14]
- 2018-03-10: Zedling Council Meeting 2018-03-10[15]
- 2018-02-24: Zedling Council Meeting 2018-02-24[16]
- 2018-02-10: Zedling Council Meeting 2018-02-10[17]
- 2018-01-27: Zedling Council Meeting 2018-01-27[18]
- 2018-01-13: Zedling Council Meeting 2018-01-13[19]
- 2017-12-30: Zedling Council Meeting 2017-12-30[12]
- 2017-12-16: Zedling Council Meeting 2017-12-16[20]
- 2017-12-02: Zedling Council Meeting 2017-12-02[21]
- 2017-11-18: Zedling Council Meeting 2017-11-18[8]
- 2017-11-04: Zedling Council Meeting 2017-11-04[22]
- 2017-10-21: Zedling Council Meeting 2017-10-21[4]
- 2017-10-07: Zedling Council Meeting 2017-10-07[23]
- 2017-09-23: Zedling Council Meeting 2017-09-23[24]
- 2017-09-09: Zedling Council Meeting 2017-09-09[25]
- 2017-08-26: Zedling Council Meeting 2017-08-26[26]
- 2017-08-12: Zedling Council Meeting 2017-08-12[27]
- 2017-07-29: Zedling Council Meeting 2017-07-29[7]
- 2017-07-15: Zedling Council Meeting 2017-07-15[28]
- 2017-07-01: Zedling Council Meeting 2017-07-01[29]
- 2017-06-17: Zedling Council Meeting 2017-06-17[30]
- 2017-06-03: Zedling Council Meeting 2017-06-03[31]
- 2017-05-20: Zedling Council Meeting 2017-05-20[32]
- 2017-05-07: Zedling Council Meeting 2017-05-07[33]
- 2017-04-22: Zedling Council Meeting 2017-04-22[34]
- 2017-04-08: Zedling Council Meeting 2017-04-08[35]
- 2017-03-25: Zedling Council Meeting 2017-03-25[36]
- 2017-03-11: Zedling Council Meeting 2017-03-11[37]
- 2017-02-25: Zedling Council Meeting 2017-02-25[11]
- 2017-02-11: Zedling Council Meeting 2017-02-11[38]
- 2017-01-28: Zedling Council Meeting 2017-01-28[6]
- 2017-01-14: Zedling Council Meeting 2017-01-14[10]
- 2016-12-17: Zedling Council Meeting 2016-12-17[39]
- 2016-12-03: Zedling Council Meeting 2016-12-03[40]
- 2016-11-19: Zedling Council Meeting 2016-11-19[41]
- 2016-11-05: Zedling Council Meeting 2016-11-05[42]
- 2016-10-22: Zedling Council Meeting 2016-10-22[43]
- 2016-10-08: Zedling Council Meeting 2016-10-08[44]
- 2016-09-24: Zedling Council Meeting 2016-09-24[45]
- 2016-09-10: Zedling Council Meeting 2016-09-10[46]
- 2016-08-27: Zedling Council Meeting 2016-08-27[9]
- 2016-08-13: Zedling Council Meeting 2016-08-13[47]
- 2016-07-30: Zedling Council Meeting 2016-07-30[5]
- 2016-07-16: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=2169[48]
- 2016-07-02: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=2156
- 2016-06-18: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=2144
- 2016-06-04: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=2119
- 2016-05-21: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=2103
- 2016-05-07: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=2073
- 2016-04-23: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=2047
- 2016-04-09: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=2025
- 2016-03-26: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=2004
- 2016-03-12: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1989
- 2016-02-27: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1970
- 2016-02-20: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1957 [Special Zedling meeting for 1.9 prep]
- 2016-02-13: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1942
- 2016-01-30: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1929
- 2016-01-17: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1908
- 2016-01-02: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1886
- 2015-12-20: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1872
- 2015-12-05: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1849
- 2015-11-21: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1833
- 2015-11-07: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1816
- 2015-10-24: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1800
- 2015-01-10: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1790
- 2015-09-26: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1778
- 2015-09-12: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1763
- 2015-08-29: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1735
- 2015-08-15: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1702
- 2015-08-01: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1667
- 2015-07-18: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1621
- 2015-07-04: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1591
- 2015-06-20: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1560
- 2015-06-06: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1522
- 2015-05-23: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1493
- 2015-05-09: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1474
- 2015-04-11: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1428
- 2015-03-21: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1385
- 2015-03-07: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1356
- 2015-02-21: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1324
- 2015-02-07: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1292
- 2015-01-24: [Notes missing, Agenda here: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1232]
- 2015-01-10: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1212
- 2014-12-27: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1179
- 2014-12-13: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1167
- 2014-12-06: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1152
- 2014-11-23: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1132
- 2014-10-26: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1102
- 2015-10-04: https://zedwork.co.uk/forum/viewtopic.php?f=3&t=1091
Previous Members
[May include current members with previous terms]]
- FunkyTechnician [ 2017-01-28 - 2018-04-21 ]
- WolfGuy_ [ 2018-01-13 - 2018-04-21 ]
- EmpressBethany [ 2017-04-08 - 2017-04-21 ]
- AmirTheTurtle [ 2017-07-15 - 2018-02-10 ]
- Entity009 [ 2017-09-23 - 2018-02-10 ]
- stumps290 [resignation] [ 2017-12-16 - 2018-01-27 ]
- Haztec [ 2017-06-03 - 2018-01-27 ]
- drbwen [ 2017-04-22 - 2017-11-04 ]
- Quicunque [ 2017-08-12 - 2017-11-04 ]
- Tjob [ 2017-07-01 - 2017-09-09 ]
- ElixirL [ 2016-08-13 - 2017-08-26 ]
- Haztec [ 2015-12-20 - 2017-04-22 ]
- One227 [ 2016-12-03 - 2017-03-25 ]
- MsKizz [ 2016-07-02 - 2017-03-25 ]
- Werble [ 2016-12-17 - 2017-03-11 ]
- ScarySpider [ 2015-03-21 - 2017-02-11 ]
- Skappy [ 2016-07-30 - 2017-01-28 ]
- Wolvergal [ 2016-09-10 - 2017-01-28 ]
- Cactusus [ 2016-10-08 - 2016-12-17 ]
- RageSquid [ 2016-06-04 - 2016-12-03 ]
- Tjob [ 2016-07-16[48] - 2016-11-05 ]
- EarthCow [ 2016-01-02 - 2016-11-05 ]
- Etho_ [ 2016-02-27 - 2016-11-22 ]
- PurpleTurtle42 [ 2016-05-21 - 2016-08-08 ]
- DarthDuck84 [ 2016-02-13 - 2016-07-30 ]
- QueenZoe [resignation] [ 2016-05-07 - 2016-07-16 ][48]
- OPNOOB [ 2016-03-26 - 2016-07-16 ][48]
- _Skyhorse [ 2015-11-21 - 2016-06-04 ]
- dracoh_12 [ 2016-03-12 - 2016-05-21 ]
- KhasOrn [ 2016-01-30 - 2016-05-21 ]
- LoneBit [ 2016-01-16 - 2016-05-07 ]
- BengalBoi [resignation] [ ????-??-?? - 2016-02-27 ]
- Suzie1 [resignation] [ 2015-09-26 - 2016-02-27 ]
- RageSquid [ 2015-10-10 - 2016-01-30 ]
- __Laurens__ [ 2014-09-20 - 2016-01-16 ]
- EarthCow [ 2016-09-12 - 2016-01-02 ]
- BigBuilderAl [ 2015-10-01 - 2016-01-02 ]
- Raysun [ 2015-11-07 - 2015-12-05 ]
- gigabite123 [ 2015-08-29 - 2015-11-21 ]
- IProBlanchard [ 2015-03-07 - 2015-11-21 ]
- lilweeph [resignation] [ 2015-06-06 - 2015-11-21 ]
- Werble23 [resignation] [ 2015-05-09 - 2015-11-21 ]
- GrimTent [ 2015-08-29 - 2015-11-07 ]
- echosong421 [ 2014-12-27 - 2015-10-24 ]
- GEMINI7099 [ 2014-12-06 - 2015-09-12 ]
- Ecauzey [ 2015-04-11 - 2015-07-18 ]
- haggisboy69 [????-??-?? - 2015-08-15]
- DannyC96 [ 2014-12-13 - 2015-08-15 ]
- Memery [ 2014-09-20 - 2015-08-15 ]
- FlipJe2Go [ 2014-10-26 - 2015-05-23 ]
- bartman51 [ ????-??-?? -2015-05-09 ]
- Suzie1 [ 2014-11-23 - 2015-02-07 ]
- lilweeph [ 2014-09-20 - 2015-03-21 ]
- Werble23 [ 2014-09-20 - 2015-03-21 ]
- wperks26 [ ????-??-?? - 2015-03-21 ]
- NinjaNoob684 [ 2014-09-20 - 2015-03-07 ]
- Purps68 [ 2014-09-20 - 2015-03-07 ]
- GrimTent [ 2014-09-20 - 2015-03-07 ]
- k1z5 [????-??-?? - 2015-04-11]