Administrative Proposal: Reporting fix in the Bylaws

Status message

Displaying output for plurality voting

Open Votes

Proposal Type: Bylaw Revision
Opened: 24-Dec-2008 1:00AM EST
Closing: 17-Dec-2008 1:00AM EST


**This is an Administrative proposal and requires no second. If it is objected to within one week it will be required to go to vote.**

Due to the fact that a couple past votes that went through had issues due to the bylaws on the website not being updated I found an error that occurred. In December 2006 the following vote passed: chronreprt06 regarding the failure to report of chronicles which listed how this would be handled. Sadly since then the following updates have passed with the old wording of the failure to report section as copied and pasted from the bylaws from the website that were not updated with the new information. These included reporting07 and reporttwice. In order to get the bylaw inline with what it was supposed to be as passed by council and what we have been using already I am proposing the following to be changed from as listed:

D) Reporting

i) All reports are out-of-character information except as specifically and mutually agreed between Storytellers and Coordinators for the sake of story, plot or continuity.

ii) Chronicles that do not speak or write English as a primary language are encouraged to maintain contact with OWBN as above, as best they can. The Council understands that reports may not arrive in English.

iii) Chronicle reporting

(1) Each member chronicle of OWBN is required to report to the Archivist, Head Coordinator (HC), and Assistant Head Coordinators (AHC) either in writing via email, or via the appropriate Internet submission form on the OWBN website.

(2) The report may be written by any member of the storytelling staff of each chronicle, but must be submitted by either the HST or Council Member, to ensure its validity. These reports shall be due on the first day of February and August.

(3) Chronicle reports are to be submitted in order to:

(a) Keep track of your Chronicle so we know you're still operational.

(b) Track who is supposed to be on which global administrative lists.

(c) Deal with inter-chronicle disputes as they arise.

(d) Log any issues the chronicles may have.

(e) Encourage interaction with less vocal chronicles.

(f) Maintain an approximate census of our population.

(g) Keep record of major events within chronicles.

(4) Historical Report

(a) This report shall consist of:

(i) Chronicle Name/Appellation/Location.

(ii) List of Council Member and storytelling team (including e-mail addresses and/or phone number for emergency access).

(iii) Current chronicle web page address.

(iv) Dates of game(s) played that month.

(v) Approximate attendance.

(vi) In-character (IC) events that may affect the plots of other chronicles.

(vii) Inter-chronicle interactions that affect the plots of any other member chronicles.

(viii) Other matters the reporter feels are relevant.

(ix) Inner-chronicle activity consisting of:

(a) Death or Administrative Removal of prominent characters
within the chronicle.

(b) Political changes within chronicle. Ex: Camarilla domain changing to Sabbat domain, the Tremere killing all of the Toreador, the Prince banning an entire clan, Etc

File / Document: No file attachments for this vote.
Ballot Options
Autopass
Abstain