Charter - Revision history

Perle: Voter approved charter changes implemented.

2024-11-21T15:50:17Z

Voter approved charter changes implemented.

Perle at 15:19, 21 November 2024

2024-11-21T15:19:57Z

Paazin: /* Election Cycles */

2020-08-31T13:44:51Z

‎Election Cycles

Foambats4all: Fix copy/paste error.

2014-05-02T14:41:03Z

Fix copy/paste error.

Foambats4all: Provide linkings for admin positions.

2014-04-30T21:42:46Z

Provide linkings for admin positions.

Foambats4all: Protected "Charter" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2014-02-05T21:33:35Z

Protected "Charter" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Foambats4all: /* Lead Veto */

2014-02-04T18:52:30Z

‎Lead Veto

Foambats4all at 06:25, 4 February 2014

2014-02-04T06:25:51Z

Show changes

Foambats4all: /* Domains */

2014-02-04T06:23:52Z

‎Domains

Foambats4all at 23:31, 22 January 2014

2014-01-22T23:31:23Z

@@ Line 19: / Line 19: @@
 === Administrators (Admin) ===
-There shall be three ALFA Administrators. Each shall be specifically elected to, and have responsibility for, a particular domain. No one person may administrate more than one domain at a time.
+There shall be three ALFA Administrators. Each shall be specifically elected to, and have responsibility for, a particular domain. No one person may be administrator of more than one domain at a time.
 ==== Domains ====
 The three administrative domains are:
-* '''[[Lead Administrator]] (LA)''' — Oversight of Administration, Veto & Referral Authority, Election Oversight, and Public Relations. Also responsible for resolving disputes over domain classification of any particular issue.
+* '''[[Lead Administrator]] (LA)''' — Oversight of Administration, Veto & Referral Authority, Election Oversight, and Public Relations, Vault[Azure], FTP and Website.  Also, responsible for resolving disputes over domain classification of any particular issue.
-* '''[[Dungeon Master Administrator | DM Administrator]] (DMA)''' — Oversight of DMs & Servers including Item Compliance, Global Plots & Quests, DM Approval & Discipline, among others.
+* '''[[Technical Administrator]] (TA)''' — ACR/HAK and other in-game coding, scripting, and software issues. Tech admin is also in charge of Standards, HDM, DM, and Server Approvals.
-* '''[[Technical Administrator]] (TA)''' — ACR/HAK and other in-game coding, scripting, and software issues.
+* '''[[Player Administrator]] (PA)''' — Applications, Guilds, ALFA Player’s Manual, ALFA Representatives, Player Discipline, chat (Discord, etc) and Player Acceptance.
 ==== Cross-Domain Issues ====
@@ Line 35: / Line 33: @@
 HDMs are those people with ultimate responsibility for a server area. HDMs have broad discretion over who is on their server staff and how their server is run. As such, HDMs are held totally responsible for their server, including the content of their modules and the behavior of DMs on their server staff. HDMs are obligated to follow ALFA global standards as determined by the Administration.
-All HDMs are responsible for providing monthly back-up copies of their servers to the DM Administrator. Modules that become part of ALFA are subject to section 5 of this Charter. For any HDM who leaves ALFA, through his or her own volition or otherwise, the most recent back-up version of their mod may continue to be used by the ALFA community. Out of common courtesy, departing HDMs are expected to provide the ALFA Administrators with the most recent back-ups of their servers for future DMs.
+All HDMs are responsible for providing monthly back-up copies of their servers to the GIT Platform for ALFA . Modules that become part of ALFA are subject to section 5 of this Charter. For any HDM who leaves ALFA, through his or her own volition or otherwise, the most recent back-up version of their mod may continue to be used by the ALFA community. Out of common courtesy, departing HDMs are expected to provide the ALFA Administrators with the most recent back-ups of their servers for future DMs.
-Oversight of HDMs, including the addition of new HDMs and the removal of existing ones, is the purview of the DM Administrator.
+Oversight of HDMs, including the addition of new HDMs and the removal of existing ones, is the purview of the TA Administrator.
 === Dungeon Masters (DM) ===
 DMs are members of the server staff of each server. DMs are appointed and removed at the will of their HDM.
-Oversight of DMs is the purview of the DM Administrator.
+Oversight of DMs is the purview of the TA  Administrator.
 === ALFA Representatives (AR) ===
@@ Line 65: / Line 63: @@
 * June — Lead Admin
 * August — Player Admin
 * November — Technical Admin
@@ Line 76: / Line 72: @@
 ==== Voting Constituencies ====
-The voting constituencies for Infra, Tech, and DM Administrators shall include all seated Administrators, all HDMs, vote-eligible Administrator Staff as defined in section 3.5, and all DMs. The same shall hold for recall votes (as defined in section 3.4) involving these Administrators.
+The voting constituencies  for Tech, Lead, and Player Administrators shall include all members of ALFA. The same shall hold for Tech, Lead, and Player Administrators recalls.
 ==== Deciding Elections ====
@@ Line 105: / Line 99: @@
 The Lead Administrator shall be charged with ensuring that as fair and as impartial elections as possible shall be held. This includes working with members of the Website and Server staff to create anonymous, yet verifiable, databases of voters, auditing elections, and conveying the audited results to the community, or the appropriate Administrator, in case of a tie.
-If there is no sitting Lead Administrator, or if sitting Lead Administrator is running in the elections, then the Election Oversight shall fall to the Player Administrator. If there is neither a sitting Lead Administrator nor a sitting Player Administrator, or both are running simultaneously, one of the other three Administrators will decide via a majority vote amongst themselves which of them will oversee the election.
+If there is no sitting Lead Administrator, or if a sitting Lead Administrator is running in the elections, then the Election Oversight shall fall to the Player Administrator. If there is neither a sitting Lead Administrator nor a sitting Player Administrator, or both are running simultaneously, the other Administrators will decide who will oversee the election.
 === Recall ===
@@ Line 149: / Line 143: @@
 == Amending the Charter ==
-Only the Lead Administrator may make formal proposals for amendments and revisions to the ALFA Charter. Proposals from the Lead Administrator must be approved by at least three Admin, and at least 2/3 of a combined vote of the HDMs, vote-eligible Administrator Staff as defined in section 3.5, and DMs casting votes, for the matter to be implemented
+Only the Lead Administrator may make formal proposals for amendments and revisions to the ALFA Charter. Proposals from the Lead Administrator must be approved by at least two Admins, and at least 2/3 of a combined vote of the HDMs, vote-eligible Administrator Staff as defined in section 3.5, and DMs casting votes, for the matter to be implemented.

@@ Line 19: / Line 19: @@
 === Administrators (Admin) ===
-There shall be five ALFA Administrators. Each shall be specifically elected to, and have responsibility for, a particular domain. No one person may administrate more than one domain at a time.
+There shall be three ALFA Administrators. Each shall be specifically elected to, and have responsibility for, a particular domain. No one person may administrate more than one domain at a time.
 ==== Domains ====
-The five administrative domains are:
+The three administrative domains are:
 * '''[[Lead Administrator]] (LA)''' — Oversight of Administration, Veto & Referral Authority, Election Oversight, and Public Relations. Also responsible for resolving disputes over domain classification of any particular issue.
 * '''[[Dungeon Master Administrator | DM Administrator]] (DMA)''' — Oversight of DMs & Servers including Item Compliance, Global Plots & Quests, DM Approval & Discipline, among others.

@@ Line 61: / Line 61: @@
 ==== Election Cycles ====
 The monthly election schedule will be:
-* June & December: Lead Admin
+The election schedule will be:
-* August & February: Player Admin
-* March & September: Infrastructure Admin
+* June — Lead Admin
-* April & October: DM Admin
+* August — Player Admin
-* May & November: Technical Admin
+* September — Infrastructure Admin
 The self-nomination period for candidates will open on the first day of the relevant month and proceed for seven days, closing on the seventh of that month. On the eighth of that month, voting will be opened for the appropriate constituency. The initial vote in an election shall last for four days. Runoff votes, if required, shall last for three days beginning as soon as possible after the first round.

← Older revision		Revision as of 14:41, 2 May 2014
Line 147:		Line 147:

	== Amending the Charter ==		== Amending the Charter ==
−	Only the Lead Administrator may make formal proposals for amendments and revisions to the ALFA Charter. Proposals from the Lead Administrator must be approved by at least three Admin, and at least ? of a combined vote of the HDMs, vote-eligible Administrator Staff as defined in section 3.5, and DMs casting votes, for the matter to be implemented	+	Only the Lead Administrator may make formal proposals for amendments and revisions to the ALFA Charter. Proposals from the Lead Administrator must be approved by at least three Admin, and at least 2/3 of a combined vote of the HDMs, vote-eligible Administrator Staff as defined in section 3.5, and DMs casting votes, for the matter to be implemented

@@ Line 23: / Line 23: @@
 ==== Domains ====
 The five administrative domains are:
-* '''Lead Administrator (LA)''' — Oversight of Administration, Veto & Referral Authority, Election Oversight, and Public Relations. Also responsible for resolving disputes over domain classification of any particular issue.
+* '''[[Lead Administrator]] (LA)''' — Oversight of Administration, Veto & Referral Authority, Election Oversight, and Public Relations. Also responsible for resolving disputes over domain classification of any particular issue.
-* '''DM Administrator (DMA)''' — Oversight of DMs & Servers including Item Compliance, Global Plots & Quests, DM Approval & Discipline, among others.
+* '''[[Dungeon Master Administrator | DM Administrator]] (DMA)''' — Oversight of DMs & Servers including Item Compliance, Global Plots & Quests, DM Approval & Discipline, among others.
-* '''Technical Administrator (TA)''' — ACR/HAK and other in-game coding, scripting, and software issues.
+* '''[[Technical Administrator]] (TA)''' — ACR/HAK and other in-game coding, scripting, and software issues.
-* '''Infrastructure Administrator (IA)''' — Vault, IRC, FTP, & Website.
+* '''[[Infrastructure Administrator]] (IA)''' — Vault, IRC, FTP, & Website.
-* '''Player Administrator (PA)''' - Applications, Guilds, ALFA Player’s Manual, ALFA Representatives, Player Discipline, and Player Acceptance.
+* '''[[Player Administrator]] (PA)''' - Applications, Guilds, ALFA Player’s Manual, ALFA Representatives, Player Discipline, and Player Acceptance.
 ==== Cross-Domain Issues ====

← Older revision	Revision as of 21:33, 5 February 2014
(No difference)

@@ Line 117: / Line 117: @@
 === Lead Veto ===
-The Lead Administrator can veto any decision by any other administrator within thirty days of the decision. To override the Lead’s veto, three other members of the Administration must agree to propose a vote for an override to the HDMs. At least ? (two thirds) of voting HDMs must support the override for it to be effective. Vote-eligible Administrator Staff and DMs are not able to participate in the veto override procedure.
+The Lead Administrator can veto any decision by any other administrator within thirty days of the decision. To override the Lead’s veto, three other members of the Administration must agree to propose a vote for an override to the HDMs. At least 2/3 (two thirds) of voting HDMs must support the override for it to be effective. Vote-eligible Administrator Staff and DMs are not able to participate in the veto override procedure.
 === General Authorities ===

← Older revision		Revision as of 23:31, 22 January 2014
Line 1:		Line 1:
		+	[[Category:Legislation]]
		+
	''"If I have seen a little further, it is by standing on the shoulders of Giants." — Sir Isaac Newton''		''"If I have seen a little further, it is by standing on the shoulders of Giants." — Sir Isaac Newton''