L Admin
The SWRP Staff Team has agreed to my request that we do a rare, open forum, public vote. How this works:
1. This can operate as a normal feedback/suggestion forum thread, as the community can weigh in and discuss and try to persuade the Staff team with their discussions of voting one way or the other.
2. It's not a poll. Sometimes, the Staff Team will run votes without running polls, because it's a smaller forum of votes.
3. RPJs will not be included in this vote, but may still weigh in or even "vote" to have their positions officially registered, in spirit.
What's normal:
1. I think we have 100% Admin attendance this week, so we will wait on all votes. Community, we usually do this in private to avoid the pressure of the community, so become aware that Admins have lives and can't just be summoned to vote on your favorite thing at a dime's notice, I do not pay these people. Avoid pressuring Admins for timeliness.
2. I am requiring a super majority (66% of the vote) for this measure to pass. An Abstain in this situation is usually a win for the "yes" votes, as it lessens the ceiling for a simple majority, but it does still officially record the Admin's official position on the issue discussed. But basically, we can only afford to lose one Admin vote - unless the other potential "no" is convinced to become an "Abstain".
3. As always, if a "no" vote is issued, the Admin needs to qualify their "no". "Yes" votes do not need to be qualified. This means a reason must be appended, but it can be any reason.
4. Tefka and Valiens hold a veto. This means if Tefka or Valiens, as Head Administrators, writes their intent to vote with a veto, the entire measure must fail. A simple "no" from a Head Administrator does not issue the Veto - the Head Admin must clearly make it known they are intending to sink the entire vote with their Veto.
----------------------------
Tef's Proposal
Tef's Notes
What I believe this solves: It creates a "invasion draft" like dodgeball and gives the MFOs more granular authority, while also completely preventing a "blanket approval" situation. The Ally List must be approved several times during this process, by multiple people, creating several instances in which issues or "blanket approvals" may be caught. It also provides more importance on the ally slots themselves, rather than creating a "free for all" environment where it's just accepted that pretty much anyone can join the Invasion (which also invalidates the purpose of having ally rules.)
What I believe this helps: It seems the definition of Ally has been taken too literally by the Staff Team and the community, to the point of dictation the direction of roleplay players may write. This removes a lot of the responsibility on Staff's shoulders in this decisions, as allies require both Major Faction Owner's consent to join.
Problems this creates: Valiens made the best point in private deliberation - it creates decisions that can be used tactically, so it is inevitable that it will be used tactically. That's kind of my intent, but it is very obvious how it could be used negatively, as a single Major Faction could potentially deny all possibility for all allies. However, I do not believe this is Staff's problem, lol. I realize that it can create increased tension between Major Faction Owners, but I also believe 1) Major Faction Owners are held to higher standards, and if one is deemed a problem in the culture, they can be removed and 2) I do not think the SWRP Staff Team should default to "Denying allies is bad." It is bad, yes, for the black and white interpretation of getting more posts on the website - but I also think we can afford this, in effort to make allies more special, and to keep the spirit of Invasions.
1. This can operate as a normal feedback/suggestion forum thread, as the community can weigh in and discuss and try to persuade the Staff team with their discussions of voting one way or the other.
2. It's not a poll. Sometimes, the Staff Team will run votes without running polls, because it's a smaller forum of votes.
3. RPJs will not be included in this vote, but may still weigh in or even "vote" to have their positions officially registered, in spirit.
What's normal:
1. I think we have 100% Admin attendance this week, so we will wait on all votes. Community, we usually do this in private to avoid the pressure of the community, so become aware that Admins have lives and can't just be summoned to vote on your favorite thing at a dime's notice, I do not pay these people. Avoid pressuring Admins for timeliness.
2. I am requiring a super majority (66% of the vote) for this measure to pass. An Abstain in this situation is usually a win for the "yes" votes, as it lessens the ceiling for a simple majority, but it does still officially record the Admin's official position on the issue discussed. But basically, we can only afford to lose one Admin vote - unless the other potential "no" is convinced to become an "Abstain".
3. As always, if a "no" vote is issued, the Admin needs to qualify their "no". "Yes" votes do not need to be qualified. This means a reason must be appended, but it can be any reason.
4. Tefka and Valiens hold a veto. This means if Tefka or Valiens, as Head Administrators, writes their intent to vote with a veto, the entire measure must fail. A simple "no" from a Head Administrator does not issue the Veto - the Head Admin must clearly make it known they are intending to sink the entire vote with their Veto.
----------------------------
Tef's Proposal
REQUESTING AID
1. Starting on the day of the Invasion Declaration OOC thread, the assigned Invasion Admin from the SWRP Staff Team (once assigned) will open communication with the involved Major Faction Owners and give them a "Ally Number."
2. An Ally Number is the number of total Allies that may join the thread without being members of either Major Faction. This number may change depending on the assigned Invasion Admin's decision, but as a foundation, the official recommended number is anywhere between 10-20.
3. Upon receiving the Ally Number, involved Major Faction Owners must create an Ally List. The Ally List will possess the names of all approved allies permitted to join the Invasion without joining the Major Factions. The maximum number of allies on this list may not exceed the Ally Number.
4. Major Faction Owners must agree together on each member of the Ally List. This simulates a sort of "draft" for selecting allies.
5. There is no set default percentage or number of slots granted to each Major Faction participating. e.g. A single Major Faction can deny all allies. A single Major Faction may forfeit all claims it may have to the ally list, and give its potential share to the opposing Major Faction.
6. Once the list is finalized, and all Major Faction Owners agree, it must be sent to the Invasion Admin. The Invasion Admin will then verify with the Major Faction Owners that all are in agreeance. Allies may not join the Invasion until the Invasion Admin officially accepts the Ally List.
7. After the list has been accepted, removing and adding more allies requires the same approval process from both Major Faction Owners.
8. The Invasion Admin, as always, can remove any name for any reason from this list.
Tef's Notes
What I believe this solves: It creates a "invasion draft" like dodgeball and gives the MFOs more granular authority, while also completely preventing a "blanket approval" situation. The Ally List must be approved several times during this process, by multiple people, creating several instances in which issues or "blanket approvals" may be caught. It also provides more importance on the ally slots themselves, rather than creating a "free for all" environment where it's just accepted that pretty much anyone can join the Invasion (which also invalidates the purpose of having ally rules.)
What I believe this helps: It seems the definition of Ally has been taken too literally by the Staff Team and the community, to the point of dictation the direction of roleplay players may write. This removes a lot of the responsibility on Staff's shoulders in this decisions, as allies require both Major Faction Owner's consent to join.
Problems this creates: Valiens made the best point in private deliberation - it creates decisions that can be used tactically, so it is inevitable that it will be used tactically. That's kind of my intent, but it is very obvious how it could be used negatively, as a single Major Faction could potentially deny all possibility for all allies. However, I do not believe this is Staff's problem, lol. I realize that it can create increased tension between Major Faction Owners, but I also believe 1) Major Faction Owners are held to higher standards, and if one is deemed a problem in the culture, they can be removed and 2) I do not think the SWRP Staff Team should default to "Denying allies is bad." It is bad, yes, for the black and white interpretation of getting more posts on the website - but I also think we can afford this, in effort to make allies more special, and to keep the spirit of Invasions.
Last edited: