[Bylaws] [Objection] [AutoPass] Updating Hosting Chronicle bylaws in regards to Chronicle Bans

THIS PROPOSAL HAS THE POTENTIAL TO AUTO-PASS

I, Chase Jelliffe, as Assistant Head Coordinator, hereby propose the following changes to Coordinator Bylaws 3.B.i.5 and 3.C.i.10.

For Bylaw 3.B.i.5, add 3.B.i.5.d and 3.B.i.5.e:

5. Within 30 days of taking office the Coordinator will list on the OWBN.net Coordinator Contact Page a default chronicle under which all scenes run by their office will be hosted, unless all parties are notified prior to the start of the scene.
a. A link to the the chronicles house rules will be provided
b. An email to the Storyteller’s list will be sent out
c. In the event of a change of default hosting chronicle, this change must be noted and announced within 30 days of the change
d. In the event that a Player receives a Chronicle Ban from the default hosting chronicle or any other local Disciplinary Action that prevents interaction with the hosting chronicle, the Coordinator must work with the Player’s Storytelling staff to find a suitable chronicle in which to host the scene.
e. In the event that a Storyteller receives a Chronicle Ban from the default hosting chronicle or any other local Disciplinary Action that prevents interaction with the hosting chronicle, the Coordinator cannot prevent the players of that Storyteller’s chronicle from interacting in Coordinator scenes or decline that Storyteller from being included in their player’s interactions with the scene or Coordinator office. The Coordinator may request another Storyteller of that Chronicle be included in those interactions, if possible.

For Bylaw 3.C.i.10, add 3.C.i.10.d and 3.C.i.10.e:

10. Within 30 days of taking office the Coordinator will list on the OWBN.net Coordinator Contact Page a default chronicle under which all scenes run by their office will be hosted, unless all parties are notified prior to the start of the scene.
a. A link to the the chronicles house rules will be provided
b. An email to the Storyteller’s list will be sent out
c. In the event of a change of default hosting chronicle, this change must be noted and announced within 30 days of the change
d. In the event that a Player receives a Chronicle Ban from the default hosting chronicle or any other local Disciplinary Action that prevents interaction with the hosting chronicle, the Coordinator must work with the Player’s Storytelling staff to find a suitable chronicle in which to host the scene.
e. In the event that a Storyteller receives a Chronicle Ban from the default hosting chronicle or any other local Disciplinary Action that prevents interaction with the hosting chronicle, the Coordinator cannot prevent the players of that Storyteller’s chronicle from interacting in Coordinator scenes or decline that Storyteller from being included in their player’s interactions with the scene or Coordinator office. The Coordinator may request another Storyteller of that Chronicle be included in those interactions, if possible.

Reasoning: These are large loop-holes that potentially allow a person or an entire chronicle to be barred from interacting with a coordinator’s office simply from a single local Disciplinary Action. This closes those loopholes. If a Coordinator wishes to barr anyone from interacting with their office, that should be addressed through mediation or through Council.

Chase Jelliffe
Assistant Head Coordinator 1