Ask someone to write down the short summary of the meeting
     - For new people / people that missed meeting
     - Full notes in PDF
     
Announce the vote
     - Close the vote ceremoniously
     - Announce winners and votes
     
   Programming Team leader: Monban
   Branding Team leader: TheSlaughterBehindTheMan
   Translation Team leader: GrbavaCigla
   Game Design Team leader: Gobbel
   Art Team leader: Luke_Connor
   Project coordinators:
     NiceMicro
     Moxvallix2
     W4e
     
Lay down the basic operating procedure
     - Basic courtesy
     - Be respectful to others.
     - This is a hobby project, most people do it for FUN after work, having other stuff going on. Respect that.
     - This is a TEAM EFFORT. Decisions should be made together. It is nice to have great ideas but please give others time to digest it.
     - Communication is key. Discuss!
     
     We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things:

#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility. 
     
Teams structure
     - Teams have their own defined responsibilities
     - A team leader is the elected leader of a team, and has jurisdiction over their team chat
     - Suggestion: don't let everyone talk, only give permissions to those who are actually working in the team (people who want to join can PM leaders). Final decision is up to the team leaders.
     - A member of a team is someone who contributes to the work
     - Team members consult with their team leaders, and team leaders guide the decisions and organize the distribution of work
     - Teams implement / work on only their respective stuff
     - Teams can have deputy leaders, it's up to the teams
     - The teams timetable / human resource management is the respective team's business
     
Leadership
     - Team leaders + project coordinators
     - Right to accept Pull requests (on the request of the programming team leader, this right can be given to more people)
     - A chatroom that everyone can join but only the leadership can talk
     - Discussing the general direction of the project
     - Resolving conflicting ideas
     
The duty of the separate teams
     - Programmer Team
          - Most of coding.
          - Backend, networking
          - Implementing the game mechanics decided by the game design team
     - Game design team
          - Game concepts
          - "Story"
          - Gameplay elements
          - Planning out the levels
     - Art team
          - Creating the assets for everything
          - Music, sound effects
          - Character design
     - Branding team
          - Website
          - Subreddit
          - Social medias
          - Keep a unified theme
          - Check how others see the project / game
          - Keeping the game properly differentiated from Among Us
     - Translation team
          - The game should be playable in many languages
          - Assets should only have decorative text no instructions
     - Playtesting team (not yet functional)
          - Checking how the game concepts work out in reality
          - Check out how buggy the implementation is
          ** The playtesting team will be activated when the leadership decides it is necessary **

The whole NextCloud or other hosting / cooperative project management debacle?
     - Pros
          - Calendar
          - Kanban board
          - Circles (gorups of people)
                - Chats or files or tasks can be shared with circles
          - File upload / sync
     - Cons
          - Buggy
          - Slow
          - Confusing