[AUTOPASS] [BYLAW REVISION] Administration Coordinator

THIS PROPOSAL HAS THE POTENTIAL TO AUTOPASS

I, Chase Jelliffe, as Assistant Head Coordinator, hereby propose the following changes to the Administrative and Coordinator Bylaws:

Coordinator Bylaw Changes

Add Bylaw 2.viii:

2. Appointed Coordinator Positions

   1. The following Coordinator positions shall be appointed by the Head Coordinator as needed until such time as the Council feels the genre requires an elected Coordinator position:

      1. Kuei-jin

      2. Archivists (up to 2 positions)

      3. Historian

      4. Hunter

      5. Hengeyokai

      6. Documents

      7. Mummy

      8. Administration Coordinator

Add Bylaw 3.A.xi, renumber current 3.A.xi as 3.A.xii:

11. Administration Coordinator

    1. Duties for the Administration Coordinator shall be:

       1. All duties described in the Administrative Bylaws.

       2. Submit proposals to the website and update them accordingly.

       3. Maintain documentation of proposal support should an Autopass proposal require it in order to Autopass.

       4. Update the website for passed Bylaw Revisions and packet updates.

       5. May fix spelling, grammatical, and formatting errors in the bylaws if it does not fundamentally change the intent of the bylaw.

    2. They may delegate any of the above powers to one or more Sub-Coordinators, who they will hold responsibility over.

       1. The appointed Coordinator, or the Head Coordinator, may remove or replace these Sub-Coordinators at will. Council may remove these Sub-Coordinators with a majority vote.

       2. The appointed Coordinator is responsible for all disputed issues that are brought before Council involving any authority delegated to their Sub-Coordinators.

    3. Both the Executive Team and the Web Team may perform these duties or give support to the Administration Coordinator should the need arise.

3.A.xii.2.i Before:

2. Proposals that impact multiple genres

   1. The Executive Team may pass before Council changes to the Code of Conduct, OWbN Charter, Character Bylaws, Administrative Bylaws, and Coordinator Bylaws following the Autopass Vote Procedure.

      1. Changes to the Character Bylaws may only be propped as [AUTOPASS] if the Executive Team member has the support of all Genre Coordinators whose genres are impacted. This support must be listed in the proposal.

3.A.xii.2.i After:

2. Proposals that impact multiple genres

   1. The Executive Team may pass before Council changes to the Code of Conduct, OWbN Charter, Character Bylaws, Administrative Bylaws, and Coordinator Bylaws following the Autopass Vote Procedure.

      1. Changes to the Character Bylaws may only be propped as [AUTOPASS] if the Executive Team member has the support of all Genre Coordinators whose genres are impacted. The additional Coordinator(s) support must either be documented and sent to the Administration Coordinator before the proposal is sent to Council or the supporting Coordinators may voice their support to Council within 48 hours.

3.C.iii.2.i Before:

3. Proposals that impact multiple genres

   1. Genre Coordinator proposals that impact multiple genres have the right to be propped as [AUTOPASS] as detailed above only if they have the support of the other Genre Coordinators whose genres are impacted.

      1. The additional Coordinator(s) support must either be documented and sent to the Executive Team before the proposal is sent to Council or the supporting Coordinators may voice their support to Council within 48 hours.

3.C.iii.2.i After:

3. Proposals that impact multiple genres

   1. Genre Coordinator proposals that impact multiple genres have the right to be propped as [AUTOPASS] as detailed above only if they have the support of the other Genre Coordinators whose genres are impacted.

      1. The additional Coordinator(s) support must either be documented and sent to the Administration Coordinator before the proposal is sent to Council or the supporting Coordinators may voice their support to Council within 48 hours.

Administrative Bylaw Changes

3.B.ii.4 Before:

2. Timeframe

   1. Proposals shall have a voting period of one week from the completion of the discussion period unless otherwise noted in subsequent bylaws.

      1. No amendments may be made to a proposal that is in the voting timeframe.

   2. The Head Coordinator may extend any vote by twenty-four (24) hour increments or multiples thereof by informing Council no later than twenty-four (24) hours before the extension. Extensions may not exceed a total timeframe of fourteen (14) additional days without a mandate from the Council.

   3. The Head Coordinator or Assistant Head Coordinator may close the vote prior to the official date if the outcome is a mathematical certainty.

   4. After the closing date for voting, the votes are counted and posted. The Web Team is responsible to update the OWBN website to reflect any changes made to the bylaws, adding Packets to our resource page, and updating any other changes ratified by Council.

3.B.ii.4 After:

3. Timeframe

   1. Proposals shall have a voting period of one week from the completion of the discussion period unless otherwise noted in subsequent bylaws.

      1. No amendments may be made to a proposal that is in the voting timeframe.

   2. The Head Coordinator may extend any vote by twenty-four (24) hour increments or multiples thereof by informing Council no later than twenty-four (24) hours before the extension. Extensions may not exceed a total timeframe of fourteen (14) additional days without a mandate from the Council.

   3. The Head Coordinator or Assistant Head Coordinator may close the vote prior to the official date if the outcome is a mathematical certainty.

   4. After the closing date for voting, the votes are counted and posted. The Administration Coordinator is responsible for updating the OWBN website to reflect any changes made to the bylaws, adding Packets to our resource page, and updating any other changes ratified by Council.

Add 3.A.viii:

7. Documentation and Facilitation of Proposal Processes

   1. The Administration Coordinator is responsible for submitting proposals to the website and updating them according to the format and processes detailed above.

   2. Should the Administration Coordinator deem a proposal to be invalid, they may pause discussion until the proposal is amended.

      1. The Administration Coordinator must clearly state why the proposal is invalid.

         1. Examples of invalid proposals include, but are not limited to: Is not formatted appropriately, doesn’t work with our framework, and/or contradicts existing bylaws

      2. The Executive Team may overrule the Administration Coordinator, in which case discussion continues.

Reasoning: Currently the Exec Team puts proposals on the website and the Web Team updates the website accordingly for passed proposals. This creates an issue where the Web Team is responsible for what passes, but doesn't have oversight or say into what is proposed. This new position combines these duties, so that one office adds proposals to the website and updates the website accordingly. We are confident that this position will see enough work to reasonably require a full Coordinator position as Exec and Web spend a significant amount of time each week doing them and require a high level of permissions on the website.