Forged Alliance Forever (FAF) is a community project of players and contributors who want to sustain and advance the game Supreme Commander: Forged Alliance.
The FAF Teams are groups of FAF contributors who are tasked with diffrent aspects of FAForever.
These are the current Team Leaders:
Trainer Team Leader
Inspektor_Kot (Secondary: HintHunter)
Community Manager
Deribus
Promotions Team Leeader:
Rowey
FAF Live Team Leader:
FtXCommando
Tournament Team Leader:
FtXCommando
Matchmaking Team Leader:
Archsimkat
Balance Team Leader:
Tagada
Games Team Leader:
Jip
Creative Team Leader:
Balthazar
Moderation Team Leader:
Giebmasse
DevOps Team Leader:
Brutus5000
We are a group of interested people in the development of the faf community. Our goals are providing opportunities to new players to develop their own skills and adapting them within the community.
This is the face of the team.
The team leader is elected by a team vote.
The team leader can be changed by the request of at least 50% of team members at any time.
The team leader is the default point of contact with the board and other teams.
If there is a team vote that results in a tie, that team leader acts as the tiebreaker.
This is the right arm of the team leader.
The person is elected by the team leader.
The deputy leader is also the point of contact if the team leader is absent.
The role given out by the FAFLive Manager in order to make managing the account as easy as
possible. This is typically given out to casters interested in helping the channel cover events but
may not have an interest in larger scope decisions regarding the channel. It can also be given to
serial event organizers that utilize the account or people interested in helping the channel
improve from a streaming setup point of view. The role can also be removed at the discretion of
the Manager.
This role is voted in by a majority of current Organizers. It represents people that have an
invested interest in improving the account across the variety of fields that FAFLive is used for
while also working to expand it beyond those fields.
It is not necessary to be an Associate first to be an Organizer, however it would definitely be the
norm. A person can apply to be part of the Organizers by speaking to the Manager of the team
who will then handle the logistics of a voting process.
Organizers vote for a new Manager on an annual basis after the annual FAF General Meeting.
In cases where a Manager must be replaced, 66% of the Organizers can submit a petition to the
Board.
TDs themselves do not hold any minimum responsibilities but are able to voice concerns and
input about tournament schedules and funding. They are free to participate in these discussions
as interest in making long term, consistent, and complex events run smoothly is the ultimate
division between a Senior TD and a standard TD.
Tournament Directors are given privileges over events as outlined by:
https://forum.faforever.com/topic/269/tournament-code-of-conduct
Senior Tournament Directors will be responsible for reviewing tournament formats and giving
advice on how to make events run optimally.
They will also be the ultimate decision body that
determines Official FAF Event Scheduling as well as working with the Board to allot funds for
these events through the Tournament Manager.
Senior TDs vote for a new Manager on an annual basis after the annual FAF General Meeting.
In cases where a Manager must be replaced, 66% of the Senior TDs can submit a petition to the Board
❖ Interested applicants apply by messaging the team lead
❖ Applicants are discussed and voted on by the team with a majority required to join, with the team leader being the tiebreak
❖ Team members may be removed due to inactivity or being no longer suitable for the position
❖ The team leader acts as the point of contact with the board and other teams
❖ The team leader is elected by the team vote or by the previous team leader
❖ Any team member can call for team lead election at any time with a 6 month cooldown period in normal situations
❖ Authority to assign team members to specific matchmaker pools
❖ Authority to determine membership and structure of the matchmaker team
❖ Curate and update 1v1, 2v2, 4v4 matchmaker pools monthly
❖ Determine the rating brackets and the pool breakdown by bracket
❖ Update the maps rating spreadsheet to assist with making pools
❖ Create matchmaker events to increase engagement with matchmaker
❖ Gather data and feedback on what maps are liked by the community
❖ Work with mapmakers to accept/give feedback to new matchmaker submissions
Being a member of the game team means you maintainer rights on the repository. This allows you to do what one expects from a maintainer. They can review and merge pull requests of contributors. And they have a vote on larger changes, such as a change to the architecture of the code. A member is encouraged to review pull requests and to interact with the community. A member is considered inactive when it has not made contributions and did not interact with the community.
A contributor can not join the team directly. They must be put forward by another member. This guarantees that at least one member is able to speak up and support the contributor. Within four weeks of being put forward the team can discuss and vote on whether the contributor is to become part of the team. The contributor is accepted once a majority votes yes. If no majority is found within four weeks the contributor is automatically declined. The lead can veto the contributor from becoming a member. This measure is rather extreme - the matter can be taken up to the board when applied and disputed by other members .
At any point the lead can eject a member from the team - the matter can be taken up to the board when applied and disputed by the member in question.
Being the lead of the game team means you have admin rights on the repository. The term 'lead' is symbolic. A better term from the scrum world would be a product owner. The lead stays in touch with the remaining teams and the board. The lead is the only person that can make a release towards the main branch: deploy/faf
.
Any member can call a re-election of the lead. By doing so they put forward another member to become lead. This guarantees that at least two members support the election. This can be done at any moment. After an election there is a two month cooling off period during which no new elections can be initiated. There's a two weeks notice for members to be made aware of the election. During this period any other member can decide to join and compete in the election. The lead automatically participates in the election unless he declines.
The election uses approval voting. This means that the person with the most approvals becomes the new lead.
We enable the promise of forever in Forged Alliance Forever.
This is achieved by following our key goals. Everything we do should be
*More details on the dev team can be found at DevOps