Difference between revisions of "Squadron Process"

From UOAF Codex
Jump to navigation Jump to search
(Minor grammar fixes)
(14 intermediate revisions by one other user not shown)
Line 1: Line 1:
[[File:UOAF Roundel clean2.png|left|frameless]]
 
 
 
 
 
 
 
 
 
 
 
 
 
 
=Team Charter=
 
=Team Charter=
 +
[[File:UOAF_Roundel_clean2.png|frameless]]
 
{| class="wikitable"
 
{| class="wikitable"
|Squadron Vision
+
|'''Squadron Vision'''
|'''We aspire to be the most fun, accessible, humble and passionate flight simulations squadron in the world'''
+
|'''<big>We aspire to be the most fun, accessible, humble, and passionate flight simulation squadron in the world</big>'''
 
|-
 
|-
|Mission
+
|'''Mission'''
 
|
 
|
*Hosting detailed, well thought-out, epic, serious fun, consistent BMS events
+
*Hosting detailed, well thought-out, epic, seriously fun, and consistent BMS events
 
*Consider engagement with other sims
 
*Consider engagement with other sims
*Hosting training events and wiki
+
*Host training events and wiki
 
*Community outreach  
 
*Community outreach  
 
**Open door
 
**Open door
 
**Creating good relationships with community leaders, content creators
 
**Creating good relationships with community leaders, content creators
**Being the example of how sim communities should aspire to
+
**Being the example which sim communities should aspire to
 
*Re-evaluation and re-assessment - data driven and collection
 
*Re-evaluation and re-assessment - data driven and collection
 
*Frequent involvement of the squadron in squadron direction and decision making
 
*Frequent involvement of the squadron in squadron direction and decision making
 
|-
 
|-
|Roles + responsibilities
+
|'''Roles + responsibilities'''
|Lead (Krause)
+
|'''Lead (Krause)'''
 
 
 
*Wringable neck for the squadron
 
*Wringable neck for the squadron
*Prioritizes backlog of work from idea funnel
+
*Prioritizes backlog of work
 
*Leads planning and squadron process as a servant leader
 
*Leads planning and squadron process as a servant leader
 
*Veto power
 
*Veto power
Line 44: Line 31:
 
*Advise current leadership but not decide anything
 
*Advise current leadership but not decide anything
  
Roster (“patched members”):  
+
'''Roster (“patched members”):'''
  
 
*Day to day moderators of the events/operations
 
*Day to day moderators of the events/operations
Line 59: Line 46:
 
*Event coordination (See below)
 
*Event coordination (See below)
  
Frag team:
+
'''Frag team:'''
  
 
*Owns standards for the frag
 
*Owns standards for the frag
Line 65: Line 52:
 
*Generating the frags
 
*Generating the frags
 
|-
 
|-
|Scope
+
|'''Scope'''
|In:
+
|'''In:'''
 
 
 
*BMS events
 
*BMS events
 
*Open to other types of gaming (e.g. DCS, IL2, Steelbeasts etc)
 
*Open to other types of gaming (e.g. DCS, IL2, Steelbeasts etc)
Line 79: Line 65:
 
*Surveying and collecting metrics
 
*Surveying and collecting metrics
 
*Server maintenance/expansion
 
*Server maintenance/expansion
 +
*Website
  
Out:
+
'''Out:'''
  
*Website
 
 
*TeamSpeak (We can use it, but we want to move toward discord)
 
*TeamSpeak (We can use it, but we want to move toward discord)
 
|-
 
|-
|Values
+
|'''Values'''
 
|
 
|
 
*Mutual learning
 
*Mutual learning
Line 97: Line 83:
 
*Punctuality
 
*Punctuality
 
|-
 
|-
|Success criteria
+
|'''Success criteria'''
 
|''How do we know if we are being successful?''  
 
|''How do we know if we are being successful?''  
 
*We have a set of KPIs here which are collected after every event. We use this data to steer improvements in the squadron.
 
*We have a set of KPIs here which are collected after every event. We use this data to steer improvements in the squadron.
 
|-
 
|-
|Risks/weaknesses
+
|'''Risks/weaknesses'''
 
|
 
|
 
*
 
*
 
|-
 
|-
|Motto
+
|'''Motto'''
 
|''Sordida Unguibus'' “Dirty fingernails” - TBD for an alternative
 
|''Sordida Unguibus'' “Dirty fingernails” - TBD for an alternative
 
|}
 
|}
  
 
=Communication=
 
=Communication=
We use Discord 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 74.91.123.42 pw: grits.  
  
 
=Documents=
 
=Documents=
Please store all documents (including ACMI) on the UOAF google drive here. '''Note that this is a public folder''', but can only be edited by the UOAF members google group which includes all patched members. IF you want to restrict access (e.g. confidential info), be sure to click the “share” button on the top right and tweak it.  
+
Please store all documents (including ACMI) on the [https://drive.google.com/drive/u/3/folders/0B01Wjtmo89sBb1J5Y2pKd2o2TWM UOAF google drive here]. '''Note that this is a public folder''', but can only be edited by the UOAF members google group which includes all patched members. IF you want to restrict access (e.g. confidential info), be sure to click the “share” button on the top right and tweak it so that only uoaf-members@googlegroups.com OR a specific subset of members can see it.  
  
 
=Planning=
 
=Planning=
  
*We use a Trello Kanban board to manage our team work
+
*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
 
*Each task (card) on the board represents a week of work or less
 
**Bigger tasks can be broken down into multiple cards
 
**Bigger tasks can be broken down into multiple cards
*Patch members can add tasks they want to happen in the funnel
+
*Patch members can add tasks they want to happen in the backlog
 
**Patch members vote for the priority tasks
 
**Patch members vote for the priority tasks
 
**Patch members should get others to vote for their tasks and generally get consensus
 
**Patch members should get others to vote for their tasks and generally get consensus
Line 126: Line 112:
 
***Items at the top should be worked on first
 
***Items at the top should be worked on first
 
**Patch members can/should work on tasks on their own initiative outside of the backlog if they want - we’re all volunteers here and no one is the boss :)
 
**Patch members can/should work on tasks on their own initiative outside of the backlog if they want - we’re all volunteers here and no one is the boss :)
*Work happens continuously, and we meet every 2 weeks before the Saturday event to reassess our backlog, progress and what we can improve (See bi-weekly agenda and process)
+
*Work happens continuously, and we meet every 2 weeks before the Saturday event to reassess our backlog, progress and what we can improve ([https://docs.google.com/document/d/1nPy_mjRFKDwJWMOmcScJXfQqwf6BZgyHvaEh7u4BrvU/edit See bi-weekly agenda and process])
 
*We discuss ongoing plans/work in #planning-and-strategy on Discord
 
*We discuss ongoing plans/work in #planning-and-strategy on Discord
  
Line 139: Line 125:
 
**Moderator: Responsible for running the event from a logistics point of view
 
**Moderator: Responsible for running the event from a logistics point of view
 
***Remote desktop, putting server in, saving mission etc
 
***Remote desktop, putting server in, saving mission etc
***Running checklists, pre and post
+
***[[UOAF Event Checklist|Running checklists, pre and post]]
***Responsible for collecting metrics afterwards. Can be collected by backup moderator, but moderator ultimately responsible.
+
***Responsible [https://drive.google.com/drive/folders/1tdt4thujx8FQiXR8qefyIObfqOjwZVCB for collecting metrics afterwards]. Can be collected by backup moderator, but moderator ultimately responsible.
 
**Assistant moderator: Also present, and will fill in for the host if he’s not there. If he is there, will assist however possible.
 
**Assistant moderator: Also present, and will fill in for the host if he’s not there. If he is there, will assist however possible.
*Servers
 
**Main: What is the primary server, and if its not documented how to maintain it, update the server documentation in this google doc
 
**Backup: If the main is down.. What do we use?
 
  
 
=Groups=
 
=Groups=
Line 154: Line 137:
 
*UOAF-leadership can manage all groups
 
*UOAF-leadership can manage all groups
  
Uoaf-members
+
[https://groups.google.com/forum/#!forum/uoaf-members Uoaf-members] aka uoaf-members@googlegroups.com
  
 
*Who: All patch members.
 
*Who: All patch members.
Line 160: Line 143:
 
*Includes “UOAF-leadership” (see below)
 
*Includes “UOAF-leadership” (see below)
  
UOAF-leadership
+
[https://groups.google.com/forum/#!forum/uoaf-leadership UOAF-leadership]
  
 
*Who: Officers/leadership team
 
*Who: Officers/leadership team
Line 166: Line 149:
 
==Trello==
 
==Trello==
  
*Trello participation is included in this team membership here
+
*Trello participation is included [https://trello.com/uoaf/members in this team membership here]
  
 
=Funding=
 
=Funding=
UOAF uses a paypal business account under the email [[Mailto:uoafdonations@gmail.com|uoafdonations@gmail.com]] .
+
UOAF uses a paypal business account under the email '''uoafdonations@gmail.com'''
  
The paypal link for recurring monthly is here. Members and stakeholders are suggested to donate to ensure continued operation of the squadron.  
+
The paypal [https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=SDFJRDJEYEDHG&source=url link for recurring monthly is here]. Members and stakeholders are suggested to donate to ensure continued operation of the squadron.  
  
 
The paypal account is currently owned by Chris Krause. Any balance is held in reserve for voting by the squadron, any deficit is currently paid for out of pocket by Chris Krause.  
 
The paypal account is currently owned by Chris Krause. Any balance is held in reserve for voting by the squadron, any deficit is currently paid for out of pocket by Chris Krause.  
  
Financial records of the paypal are to be shared with the community whenever requested.  
+
Financial records of the paypal are to be shared with the community whenever requested
 +
 
 +
=Voting in Patched Members=
 +
Anyone can initiate a vote for someone to become a patched member. The goal of voting is to gain consensus on whether or not the person in question exemplifies the values of UOAF (see above) and also is taking on the list of responsibilities of a patched member on his/her own initiative (See above), with promise to expand those responsibilities. 
 +
 
 +
We bias toward saying "No" than "Yes" and hold a very high personal conduct bar. Anyone who we can't say no to should have been a patch member already!
 +
 
 +
The squadron leader has veto power as with all things.
 +
 
 +
====Initiating a Vote====
 +
Make a post in #roster-voting, following the template:
 +
@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 />
 +
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.
 +
 
 +
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=
 
=Servers=
  
*We have the following temporary servers:
+
**Server database [https://docs.google.com/spreadsheets/d/10fiOLWnDxkIkypYJ02Ayl0EXV2-JpM8YW2UK5J2fvXE/edit#gid=0 is maintained here]
**Lukrop’s
+
**There is also a link with credentials/RDP information in it, ask leadership for a link.
**Bawki’s
 
**Briland’s
 
*We need a more permanent solution.
 
*Specs required:
 
**RAM: 16GB
 
**Upload: 2mb/s * number of clients
 

Revision as of 02:08, 8 May 2020

Team Charter

UOAF Roundel clean2.png

Squadron Vision We aspire to be the most fun, accessible, humble, and passionate flight simulation squadron in the world
Mission
  • Hosting detailed, well thought-out, epic, seriously fun, and consistent BMS events
  • Consider engagement with other sims
  • Host training events and wiki
  • Community outreach
    • Open door
    • Creating good relationships with community leaders, content creators
    • Being the example which sim communities should aspire to
  • Re-evaluation and re-assessment - data driven and collection
  • Frequent involvement of the squadron in squadron direction and decision making
Roles + responsibilities Lead (Krause)
  • Wringable neck for the squadron
  • Prioritizes backlog of work
  • Leads planning and squadron process as a servant leader
  • Veto power
  • Delegates powers to other patch members, and mentors/coaches them on execution
  • Expert-level flight sim guy

“Fellowship of the wing” (DF, Gus, Force)

  • Emeritus officers, serve as stakeholders for the squadron leadership
  • Advise current leadership but not decide anything

Roster (“patched members”):

  • Day to day moderators of the events/operations
    • Discord
  • Training
  • Flight leading
  • Package leading
  • Responsible for supporting and improving SOPs
  • Face of the squadron
  • Meet minimum competencies
    • Sharing resources to help people get to min competencies
  • Giving input and voting on what we should do next
  • Fragging/supporting events
  • Event coordination (See below)

Frag team:

  • Owns standards for the frag
    • Improving and teaching those standards
  • Generating the frags
Scope In:
  • BMS events
  • Open to other types of gaming (e.g. DCS, IL2, Steelbeasts etc)
    • Our values should apply to those games
  • Cross-community events
  • Content creation
    • Mod development
    • Videos
  • Creating/supporting a wiki (resurrect codex)
  • Everything on Discord
  • Surveying and collecting metrics
  • Server maintenance/expansion
  • Website

Out:

  • TeamSpeak (We can use it, but we want to move toward discord)
Values
  • Mutual learning
  • Being respectful
  • Be an example to others
  • Serious fun
  • Team work
  • Should accept/give feedback
  • Expertise
  • Continuous improvement
  • Punctuality
Success criteria How do we know if we are being successful?
  • We have a set of KPIs here which are collected after every event. We use this data to steer improvements in the squadron.
Risks/weaknesses
Motto Sordida Unguibus “Dirty fingernails” - TBD for an alternative

Communication

We use 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.

Documents

Please store all documents (including ACMI) on the UOAF google drive here. Note that this is a public folder, but can only be edited by the UOAF members google group which includes all patched members. IF you want to restrict access (e.g. confidential info), be sure to click the “share” button on the top right and tweak it so that only uoaf-members@googlegroups.com OR a specific subset of members can see it.

Planning

  • We use a Trello Kanban board to manage our team work
  • Each task (card) on the board represents a week of work or less
    • Bigger tasks can be broken down into multiple cards
  • Patch members can add tasks they want to happen in the backlog
    • Patch members vote for the priority tasks
    • Patch members should get others to vote for their tasks and generally get consensus
    • Lead officers considers the squadron’s feedback and metrics, pulls tasks into the backlog
      • Items at the top should be worked on first
    • Patch members can/should work on tasks on their own initiative outside of the backlog if they want - we’re all volunteers here and no one is the boss :)
  • Work happens continuously, and we meet every 2 weeks before the Saturday event to reassess our backlog, progress and what we can improve (See bi-weekly agenda and process)
  • We discuss ongoing plans/work in #planning-and-strategy on Discord

Event Planning

Identify on a Trello card:

  • Package commander: The guy who will lead the package.
  • 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
    • Event Coordinator: Responsible for making sure the entire event is executed on time, with quality and overall delivery of the event.
      • Making sure software and dependencies are up to date on the server
    • Moderator: Responsible for running the event from a logistics point of view
    • Assistant moderator: Also present, and will fill in for the host if he’s not there. If he is there, will assist however possible.

Groups

Google

  • Administered by groups.google.com
  • Used for calendar invites, document on google
  • UOAF-leadership can manage all groups

Uoaf-members aka uoaf-members@googlegroups.com

  • Who: All patch members.
  • Have edit access to the google drive location (all can view)
  • Includes “UOAF-leadership” (see below)

UOAF-leadership

  • Who: Officers/leadership team

Trello

Funding

UOAF uses a paypal business account under the email uoafdonations@gmail.com

The paypal link for recurring monthly is here. Members and stakeholders are suggested to donate to ensure continued operation of the squadron.

The paypal account is currently owned by Chris Krause. Any balance is held in reserve for voting by the squadron, any deficit is currently paid for out of pocket by Chris Krause.

Financial records of the paypal are to be shared with the community whenever requested.

Voting in Patched Members

Anyone can initiate a vote for someone to become a patched member. The goal of voting is to gain consensus on whether or not the person in question exemplifies the values of UOAF (see above) and also is taking on the list of responsibilities of a patched member on his/her own initiative (See above), with promise to expand those responsibilities.

We bias toward saying "No" than "Yes" and hold a very high personal conduct bar. Anyone who we can't say no to should have been a patch member already!

The squadron leader has veto power as with all things.

Initiating a Vote

Make a post in #roster-voting, following the template:

@Roster I'd like to nominate [@name] for roster! 
[optional reason for nomination]
Respond to this with :goodvibes:  if you think [he/she] should be one and :Disappointed:  if not. 

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.

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 is maintained here
    • There is also a link with credentials/RDP information in it, ask leadership for a link.