[Bylaw Amendment] REMOVAL OF AUTOPASS OPTION

Status message

Displaying output for plurality voting

Open Votes

Proposal Type: Bylaw Revision
Opened: 18-Jul-2014 12:00AM EDT
Closing: 25-Jul-2014 12:00AM EDT


As Council member of Winchester, Virginia: Sins in the Valley, I
hereby propose we remove the following, in entirety, from our bylaws:
Administrative 3.A.v.1.a., Administrative 3.B.iii., Administrative
3.E., Administrative 7.C.i., and Administrative 7.D.iv.

In addition, this proposal willl cause Coordinator 3.C.iii.1. be
edited to remove only item 1. “If no opposition is voiced during the
week of discussion...”, preserving 3.C.iii.1.i.”exception to above -
Player Character (PC) specific information...”.  Full texts of all
aforementioned bylaws have been included below.

These changes would not affect any proposals already in discussion
prior to when this vote goes live.

Reasoning: we should actively, rather than passively, approve changes
brought before Council.  Among additional reasons for this is the
amount of time required for information to be considered and discussed
before the decision to support it or not is made.  Especially of
concern are lengthy items such as genre packets and chronicle
applications. Autopass also creates an atmosphere where a coordinator
proposal is assumed to be the best option and it is up to council to
prove otherwise, instead of keeping the responsibility for making the
case on the shoulders of the person putting it up.

Arguments for the efficiency and time savings of autopassed props do
not outweigh dutiful and responsible reflections upon changes to the
organization.

Brian, CM SiV

Administrative 3.A.v.1.a.
If no opposition is voiced during the week of discussion, the bylaw is
considered passed and enforceable. Once passed these bylaws are
considered binding to all chronicles (as with any other bylaw) and a
chronicles refusal to adhere to said bylaw is grounds for OWBN
disciplinary measures. Opposition must be in regards to the content of
the proposal and must give those reasons why the objection is voiced.
This is to allow Coordinator's the opportunity to respond and/or make
changes/remove the proposal and its contents.

Administrative 3.B.iii.
iii. Vote Archiving of Autopass Votes
Any votes that qualify for an Autopass closing must be entered into
the voting system. The vote option shall then simply be "Autopass",
which will receive the most votes (1, by the authorized individual
closing the vote), and then be closed.
Votes to be archived and closed in this manner include, but are not
limited to: Coordinator Genre Proposals, Administrative Proposals,
Chronicle Admission Proposals, and General Consensus Proposals.

Administrative 3.E.
All proposals that meet the requirements to automatically pass shall
be recorded on the online Vote Management System as a single vote in
favor of the proposal with the comments section noting, "Automatically
Passed due to Lack of Objection."

Administrative 7.C.i.
The Admissions Coordinator, a Sub-Coordinator, or a duly appointed
representative will then submit the Application for a "Probationary
Admission" vote to the OWBN Council for the discussion period and
Admission Vote. If there are no objections during the discussion
period, the game Auto-Passes into its Probationary Period.

Administrative 7.D.iv.
iv. Any OWBN Council Member or Coordinator may post an objection to
the Admissions Coordinator to bar the chronicle from being
automatically granted full membership. The Admissions Coordinator will
then notify Council of the details of the objection.
An objection may be withdrawn at any time. If the objection is not
withdrawn, the chronicle's admission shall be taken to vote at the end
of the probationary period.

Coordinator 3.C.iii;
iii. Genre Coordinators must pass before Council any plot, enforced
policy, R&U named characters, or binding edict they wish to use which
they can reasonably expect to affect multiple chronicles and these
proposals need not be seconded, but go immediately into discussion.
If no opposition is voiced during the week of discussion, the proposal
is considered passed and enforceable. Once passed these are considered
binding to all chronicles and a chronicles refusal to adhere is
grounds for OWBN disciplinary measures. Opposition must be in regards
to the content of the proposal and must give those reasons why the
objection is voiced. This is to allow Coordinator's the opportunity to
respond and/or make changes/remove the proposal and its contents.
exception to above - Player Character (PC) specific information, such
as but not limited to PC's holding regional positions or PC's
important enough to have been included in genre documents (i.e. tribal
packets, clan packets, status packets etc.) may be updated by
notification to council, should the PC specific information change
during the duration that the document is current. Adding or removing
player characters and their respective information from genre
documents is expressly NOT covered by this clause, and should be
handled through the normal council approval processes.

latest RunningAir Jordan

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