[OWBN-Council] [PROPOSAL] [BYLAW CHANGE] Coordinator-Owned Discord Servers; Legacy and Turnover

Proposal

-------------

I, Dora Jay, cm for Tea With Dragons, do hereby propose that the following changes be made to the OWBN Coordinator Bylaws, specifically to C.i.9

This proposal requires a [SECOND] in the email subject line from a supporting chronicle.

------------------

Bylaws Now

------------------

9. Manage and set policy for any Coordinator owned; In Character or Out of Character Email lists, Wikis, Forums, Websites, or other forms of media utilized in the promotion of and or for communications of their genre. In this context, "Coordinator owned" is defined as national and international forms of the above media that are not owned and managed by local games, regional games, or PCs.

------------------

Bylaws After

------------------

9. Manage and set policy for any Coordinator owned; In Character or Out of Character Email lists, Wikis, Forums, Websites, Discord Servers, or other forms of media utilized in the promotion of and or for communications of their genre. In this context, "Coordinator owned" is defined as national and international forms of the above media that are not owned and managed by local games, regional games, or PCs.

Discord specific rules are as follows

Any Discord server designated as a “Coordinator Owned” server must have the current Coordinator's preferred Discord Account as its Root/Server Owner

All servers must be turned over via the Transfer Ownership option in Discord to the ‘New’ Coordinator's preferred Discord Account within 30 days of a finalized election

-------------

Rationale

-------------

With a third major clan now moving to Discord as their primary form of IC international / global communication; this closes the loophole that otherwise exists within the bylaws that would allow a Coordinator who, for example, did not win re-election, to remain the Root Owner of the Clan Server and have access to information they should not have access to. This also prevents the loss of logs and other vital material as it applies to the logs being passed from one coord team to another.

I’m not exactly thrilled we’re moving more and more to forced discord national communication as opposed to opt in models that support crossposting to Google Lists....but if this is the way we’re going to go, we need to make sure the current and future coord teams won’t lose access to records and data.

-------------

Change Log

-------------

1) Any Coordinator Owned Server must allow the Storytelling Staff of any game that has members participating on that server to join and be given access to see whatever their players are involved with, in the same way an email on the list might be CC’d.
to

The storytelling staff of a character always has the right to be included on any correspondence with their player base and the coordinator's office. As it applies to discord, a chronicle's staff may elect to be directly added to a server their players are part of or they may elect to receive logs as appropriate and / or upon request.

2) Split the prop into legacy turn over and ST access.