Squadron Process - Revision history

Tyrspawn at 21:44, 18 October 2024

2024-10-18T21:44:21Z

Tyrspawn at 21:43, 18 October 2024

2024-10-18T21:43:50Z

Tyrspawn at 21:41, 18 October 2024

2024-10-18T21:41:06Z

Tyrspawn at 21:39, 18 October 2024

2024-10-18T21:39:39Z

Mrkline: Clarified voting process

2024-02-24T00:14:27Z

Clarified voting process

Krause at 21:53, 23 June 2022

2022-06-23T21:53:50Z

Krause at 07:10, 17 February 2021

2021-02-17T07:10:53Z

Krause at 01:00, 12 January 2021

2021-01-12T01:00:57Z

Krause: /* Event Planning */

2021-01-12T01:00:13Z

Event Planning

Krause at 18:39, 10 January 2021

2021-01-10T18:39:22Z

@@ Line 97: / Line 97: @@
 =Planning=
-[[File:Event list.png|thumb]]
+[[File:Event list.png|thumb|alt=|none]]
 *We use threads in Discord under "Event list" to manage who is doing what in events. Each event must have a fragger and moderator. Respond to the event thread with the emoji reflecting fragger or moderator if you're going to participate.

← Older revision		Revision as of 21:43, 18 October 2024
Line 97:		Line 97:

	=Planning=		=Planning=
		+	[[File:Event list.png\|thumb]]
		+	<br />

	*We use threads in Discord under "Event list" to manage who is doing what in events. Each event must have a fragger and moderator. Respond to the event thread with the emoji reflecting fragger or moderator if you're going to participate.		*We use threads in Discord under "Event list" to manage who is doing what in events. Each event must have a fragger and moderator. Respond to the event thread with the emoji reflecting fragger or moderator if you're going to participate.

@@ Line 98: / Line 98: @@
 =Planning=
 *We use threads in Discord under "Event list" to manage who is doing what in events. Each event must have a fragger and moderator. Respond to the event thread with the emoji reflecting fragger or moderator if you're going to participate.
 *We use #event-and-squadron-planning discord channel to discuss plans and who is running events
 *We use #metrics-and-event-performance to share back performance from events.

@@ Line 98: / Line 98: @@
 =Planning=
-*We use [https://trello.com/b/tH9G6FFs/uoaf-team-board a Trello Kanban board] to manage our team work
+*We use threads in Discord under "Event list" to manage who is doing what in events. Each event must have a fragger and moderator. Respond to the event thread with the emoji reflecting fragger or moderator if you're going to participate.
-*We use #event-and-squadron-planning discord channel to discuss plans and who is running events, and put work up on Trello
+*We use #event-and-squadron-planning discord channel to discuss plans and who is running events
-*We use #metrics-and-event-performance to share back performance from events
+*We use #metrics-and-event-performance to share back performance from events.
 =Groups=
@@ Line 134: / Line 120: @@
 *Who: Officers/leadership team
-==Trello==
+==Funding==
 UOAF uses a paypal business account under the email '''uoafdonations@gmail.com'''
@@ Line 163: / Line 145: @@
 Roster members should not discuss membership - even to gauge interest - with the nominee during the voting process for a few reasons:
-# We don't want the nominee campaigning roster members to vote for them.
+#We don't want the nominee campaigning roster members to vote for them.
-# If the nomination fails (either by vote or by veto), we don't want the nominee to feel like the rug was pulled out from under them.
+#If the nomination fails (either by vote or by veto), we don't want the nominee to feel like the rug was pulled out from under them.
 The squadron leader will end the voting period, typically 72 hours after the email is sent. If the nomination succeeds, the squadron leader or a designated 2nd will reach out to the nominee and:
-# Invite them to the roster. If they accept,
+#Invite them to the roster. If they accept,
-# Confirm they have read/understood this page, and understand how we pay for our shit.
+#Confirm they have read/understood this page, and understand how we pay for our shit.
 #Get their email address and add it to google group here: https://groups.google.com/u/2/g/uoaf-members
@@ Line 178: / Line 160: @@
 *Remove from google group
 *Remove Roster tag
 *Remove AWS IAM account (if applicable)

@@ Line 20: / Line 20: @@
 |'''Lead (Krause)'''
 *Wringable neck for the squadron
 *Prioritizes squadron resources, if need be
 *Leads planning and squadron process as a servant leader
 *Veto power on decisions when there is a lack of alignment
@@ Line 158: / Line 158: @@
   @Roster I'd like to nominate [@name] for roster!
   [optional reason for nomination]
-  <nowiki>Respond to this with :goodvibes:  if you think [he/she] should be one and :Disappointed:  if not. </nowiki><br />
+  <nowiki>Respond to this with :goodvibes:  if you think [he/she] should be one and :Disappointed:  if not. </nowiki>
 Then send an email to uoaf-members@googlegroups.com letting everyone know a nomination is starting. This is to give members who are not monitoring discord a chance to see the notification, and to make sure it doesn't get buried.
-After 72 hours if complete consensus is made, the squadron leader or a designated 2nd will reach out to the individual and invite them to the roster - if they accept, we add them to the Discord @roster tag and make a hype post in #roster with mad emoticons.
+Roster members should not discuss membership - even to gauge interest - with the nominee during the voting process for a few reasons:
-Remember that they will need to be added to the Google group (Can be done by any leadership), and should also review and understand this page here on the Codex.
+# We don't want the nominee campaigning roster members to vote for them.
-=Onboarding Roster Checklist=
+The squadron leader will end the voting period, typically 72 hours after the email is sent. If the nomination succeeds, the squadron leader or a designated 2nd will reach out to the nominee and:
-*Confirm new roster has read/understood this page. And understands how we pay for our shit.
+# Invite them to the roster. If they accept,
-*Add to google group here: https://groups.google.com/u/2/g/uoaf-members
+# Confirm they have read/understood this page, and understand how we pay for our shit.
-*Add Roster tag on Discord
+#Get their email address and add it to google group here: https://groups.google.com/u/2/g/uoaf-members
-*Add to Trello team: https://trello.com/uoaf
 =Offboarding Roster Checklist=

@@ Line 20: / Line 20: @@
 |'''Lead (Krause)'''
 *Wringable neck for the squadron
-*Prioritizes backlog of work
+*Prioritizes squadron resources, if need be
 *Leads planning and squadron process as a servant leader
-*Veto power
+*Veto power on decisions when there is a lack of alignment
 *Delegates powers to other patch members, and mentors/coaches them on execution
 *Expert-level flight sim guy
 '''Roster (“patched members”):'''
@@ Line 189: / Line 184: @@
 **There is also a link with credentials/RDP information in it, ask leadership for a link.
-= Check Ride for new players =
+=Check Ride for new players=
-* New players who don't have demonstrated community experience or a community sponsor elsewhere generally need to have a "Checkride" before being allowed into a weekend multiplayer event
+*New players who don't have demonstrated community experience or a community sponsor elsewhere generally need to have a "Checkride" before being allowed into a weekend multiplayer event
-* A checkride is an evaluation of a player's capability to meet our [[SOPs/Minimum Competencies|minimum competencies]] and [[General SOPs|SOPs]]
+*A checkride is an evaluation of a player's capability to meet our [[SOPs/Minimum Competencies|minimum competencies]] and [[General SOPs|SOPs]]
-* Checkride typically take 1 hour or less and should be executed for a single prospect by an experienced roster member
+*Checkride typically take 1 hour or less and should be executed for a single prospect by an experienced roster member
-* BS1 created [https://drive.google.com/drive/u/1/folders/1KtDKo_BNAwUjjsab_q0HO7PylQP59FrU a kit for performing a checkride here] that covers all the minimum competencies and is intended to simulate a small but "full vertical" of an event.
+*BS1 created [https://drive.google.com/drive/u/1/folders/1KtDKo_BNAwUjjsab_q0HO7PylQP59FrU a kit for performing a checkride here] that covers all the minimum competencies and is intended to simulate a small but "full vertical" of an event.

← Older revision		Revision as of 07:10, 17 February 2021
Line 188:		Line 188:
	**Server database [https://docs.google.com/spreadsheets/d/183fqu-FcyYtvMTRD8Ohwxb4Zz_DkNK8--BI6hawyD7o/edit#gid=0 is maintained here]		**Server database [https://docs.google.com/spreadsheets/d/183fqu-FcyYtvMTRD8Ohwxb4Zz_DkNK8--BI6hawyD7o/edit#gid=0 is maintained here]
	**There is also a link with credentials/RDP information in it, ask leadership for a link.		**There is also a link with credentials/RDP information in it, ask leadership for a link.
		+
		+	= Check Ride for new players =
		+
		+	* New players who don't have demonstrated community experience or a community sponsor elsewhere generally need to have a "Checkride" before being allowed into a weekend multiplayer event
		+	* A checkride is an evaluation of a player's capability to meet our [[SOPs/Minimum Competencies\|minimum competencies]] and [[General SOPs\|SOPs]]
		+	* Checkride typically take 1 hour or less and should be executed for a single prospect by an experienced roster member
		+	* BS1 created [https://drive.google.com/drive/u/1/folders/1KtDKo_BNAwUjjsab_q0HO7PylQP59FrU a kit for performing a checkride here] that covers all the minimum competencies and is intended to simulate a small but "full vertical" of an event.

@@ Line 92: / Line 92: @@
 |-
 |'''Motto'''
-|''Sordida Unguibus'' “Dirty fingernails” - TBD for an alternative
+|''Sordida Unguibus'' “Dirty fingernails”
 |}

@@ Line 96: / Line 96: @@
 =Communication=
-We use [https://discord.gg/jAyjpz2 Discord (click to join)] to communicate over voice, post and share events. We can also use TeamSpeak on demand at 74.91.123.42 pw: grits.
+We use [https://discord.gg/jAyjpz2 Discord (click to join)] to communicate over voice, post and share events. We can also use TeamSpeak on demand at 87.127.93.6 pw: grits.
 =Documents=
@@ Line 104: / Line 104: @@
 *We use [https://trello.com/b/tH9G6FFs/uoaf-team-board a Trello Kanban board] to manage our team work
 *We use #event-and-squadron-planning discord channel to discuss plans and who is running events, and put work up on Trello
 *We use #metrics-and-event-performance to share back performance from events
@@ Line 110: / Line 110: @@
 Identify on a Trello card:
-*Package commander: The guy who will lead the package.
+*Package commander: The guy who will lead the package. Now on the signup sheet, used to be on Trello.
 *Mission fragger: Make the mission, test it, upload it to drive. Collaborate with others (especially package commander) to ensure quality. Make briefing and posting it.
 *Event team
@@ Line 170: / Line 170: @@
 Remember that they will need to be added to the Google group (Can be done by any leadership), and should also review and understand this page here on the Codex.
-= Onboarding Roster Checklist =
+=Onboarding Roster Checklist=
-* Confirm new roster has read/understood this page. And understands how we pay for our shit.
+*Confirm new roster has read/understood this page. And understands how we pay for our shit.
-* Add to google group here: https://groups.google.com/u/2/g/uoaf-members
+*Add to google group here: https://groups.google.com/u/2/g/uoaf-members
-* Add Roster tag on Discord
+*Add Roster tag on Discord
-* Add to Trello team: https://trello.com/uoaf
+*Add to Trello team: https://trello.com/uoaf
-= Offboarding Roster Checklist =
+=Offboarding Roster Checklist=
-* Remove from google group
+*Remove from google group
-* Remove Roster tag
+*Remove Roster tag
-* Remove from Trello team
+*Remove from Trello team
-* Remove AWS IAM account (if applicable)
+*Remove AWS IAM account (if applicable)
 =Servers=

@@ Line 104: / Line 104: @@
 *We use [https://trello.com/b/tH9G6FFs/uoaf-team-board a Trello Kanban board] to manage our team work
-*Each task (card) on the board represents a week of work or less
+*We use #event-and-squadron-planning discord channel to discuss plans and who is running events, and put work up on Trello
-**Bigger tasks can be broken down into multiple cards
+*We use #metrics-and-event-performance to share back performance from events
 ==Event Planning==
@@ Line 134: / Line 126: @@
 *Administered by groups.google.com
-*Used for calendar invites, document on google
+*Used for calendar invites, emails and [https://drive.google.com/drive/u/0/folders/0B01Wjtmo89sBb1J5Y2pKd2o2TWM managing write access to our google drive]
 *UOAF-leadership can manage all groups
@@ Line 177: / Line 169: @@
 Remember that they will need to be added to the Google group (Can be done by any leadership), and should also review and understand this page here on the Codex.
 =Servers=
-**Server database [https://docs.google.com/spreadsheets/d/10fiOLWnDxkIkypYJ02Ayl0EXV2-JpM8YW2UK5J2fvXE/edit#gid=0 is maintained here]
+**Server database [https://docs.google.com/spreadsheets/d/183fqu-FcyYtvMTRD8Ohwxb4Zz_DkNK8--BI6hawyD7o/edit#gid=0 is maintained here]
 **There is also a link with credentials/RDP information in it, ask leadership for a link.