Player Base Notification Bylaw Clarification

Status message

Displaying output for plurality voting

Open Votes

Proposal Type: Bylaw Revision
Opened: 05-Nov-2011 12:00AM EDT
Closing: 12-Nov-2011 10:58PM EST


I think this is pretty clear.   

It clarifies that STs can know everything that happens with Council, both the list and the website (voting included), that for purposes of the player base notification they are separate and can thus know everything a CM knows, and that the HC can't say that they can't on his own.  This is how we've been running things, but it deserves clarification.

It says that subcoords can be told stuff related to their jobs by Coordinators.  This is probably how things have been going.

It says that five members of council can force the HC to use his power to run a vote on an issue, including all vote options they want (IE, no only two options and both options can't be "keep everything secret."), thus allowing council to rule on sharing material or overrule the HC, and that this can be done even if the HC says no, or another bylaw says that something can or can't be shared.  

Since originally posted (this was not initially a formal proposal) I have worked to amend this so that the Web Coordinator and team can do their job.  I also removed a line that allowed people to designate how their proposal might be shared, as it could allow them to restrict proposals that should be public.  


I hereby propose that Administrative Bylaw 3.D be changed from:

Player Base Notification
  1. Rules, organizational, and/or game mechanics proposals shall be posted in their entirety on the public OWBN web site for review by the OWBN player base.
    1. This shall be done by an AHC within twenty-four (24) hours of the vote opening.
    2. The Head Coordinator may also indicate additional locations that proposals may be posted.
  1. Any vote results, including comments posted on the online Vote Management System, that relate to a rules, organizational, and/or game mechanics proposal shall be posted in its entirety on the public OWBN web site for review by the OWBN player base.
    1. This shall be done by an AHC within twenty-four (24) hours of the vote opening.
    2. The Head Coordinator may also indicate additional locations that proposals may be posted.
  1. If there should be any question on the appropriateness of players viewing the proposal, the Head Coordinator shall have final adjudicating authority on the posting of said proposal. The HC may call, if necessary, for an immediate vote from Council to clarify whether the proposal should be publicly posted. Such a call for an immediate vote on this subject will place said proposal on hold until the vote is finalized.
to:
Player Base Notification
  1. Rules, organizational, and/or game mechanics proposals shall be posted in their entirety on the public OWBN web site for review by the OWBN player base.
    1. This shall be done by an AHC or any other person the Head Coordinator designates within twenty-four (24) hours of the vote opening.
    2. The Head Coordinator may also indicate additional locations that proposals may be posted.
  1. Any vote results, including comments posted on the online Vote Management System, that relate to a rules, organizational, and/or game mechanics proposal shall be posted in its entirety on the public OWBN web site for review by the OWBN player base.
    1. This shall be done by an AHC or any other person the Head Coordinator designates within twenty-four (24) hours of the vote opening.
    2. The Head Coordinator may also indicate additional locations that proposals may be posted.
  • If there should be any question on the appropriateness of players viewing the proposal, the Head Coordinator shall have adjudicating authority on the posting of said proposal, except if a vote of council has taken place on it's posting. The HC may call for an immediate vote from Council to clarify whether the proposal should be publicly posted. Such a call for an immediate vote on this subject will place said proposal on hold until the vote is finalized. If five or more voting members of Council call for such a vote on the posting of a proposal on council, the Head Coordinator must immediately hold this vote, with all voting options asked for by the council members included, and this vote's results are binding and may overrule the Head Coordinator and the bylaws. 
  1. Chronicle Storytellers may always, regardless of the HC's authority, be fully informed of, and provided with, all material and information sent to, related to, or received from OWBN Council and it's e-mail list, including but not limited to e-mails, proposals and website information regarding voting. For the purpose of the Player Base notification bylaw Storytellers are not considered players.  Subcoordinators may be provided with the same by their Coordinator, but only if it concerns the Coordinator's powers, duties and responsibilities under the bylaws. 
Also: Add Coordinator Bylaw 3.A.vi.2.c  Web Coordinator Subcoordinators may have access to the OWBN-COUNCIL e-mail lists at the Web Coordinator's discretion.    
I also ask that if there are issues of vagueness, conflicts with other bylaws, grey areas, multiple interpretations, ways that the intended goals could be overruled, etc. that anybody sees that they share it with council so this can be amended. Preferably during the discussion  I'd like to think that would go without saying, but apparently that's not always so.  
Sincerely,
Jacob Siebert
Always Comes Evening (San Francisco, CA) Council Rep

latest jordansSneakers

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