It seems like MF2 is facing major organizational and technical hurdles and I (along with other people who have been running MF2 these days) have figured out that this is probably because of a lack of a clear process for:

a) joining MF2 as a speaker and all the steps needed to get to the mainstage,

b) having a good transition flow from speaker to speaker,

c) not giving speakers and audience conflicting information

d) a clear and policy for what to do if a speakers is very late, doesn't show up

e) solving urgent problems with the stream (audio not working, bad quality, etc)

f) having a better way to give signals to each other and mainly to hosts (e.g. a speaker passed the checks and is ready to present, somebody has not arrived, the audio is not working and an urgent break is needed).

Everybody (speaker - players) has been struggling with all the above. The reason is that there is a lack of management and of clear roles and accountability. It is important to standardize the process and make it clear to everybody so as to avoid the problems that have been plaguing Metafest.

It is also important to get rid of inefficient processes and aim for simpler and more intuitive processes if possible.

• People have been constantly facing trouble with Edumeet.
  • It’s a new platform, and people often had difficulties connecting using it.
  • There have been recurring audio connection issues.
• People who come to present often don’t know where to go and how
  • Cases:
    • Mo Casso said she was given a Google Meet link and was waiting there while people have been sharing wrong links.
    • Terry Kilby was expecting to present in the Discord.
• People need to have the speaker role to see speaker-guides and they usually are given the role very late, so they don’t have time to read and test

Possible Solutions:

• If the backstage testing is the first part of the process then people should be given the backstage link right away and told to be there 15-10 minutes before. If this has not been done in booking, someone should be in charge of seeing when the next guest has entered and to lead them to backstage. But one has to always be in backstage and make sure that they at least go through the standard quality testing process outlined by lawnmower:

  

  Press SPACE to make the image big.

• We could have the speaker guide channel open to everyone without the speaker role, or have the once that enter the server as speakers choose the role when they enter.

  • We can include the step of going to the speaker-guide channel in the info booth right away (if editing the dyno announcement is still possible) and have the speaker-guide channel (as well as all other info channels) closed to messages.
  • The second might lead to people who are not speakers pushing the button and seeing the channel but this is not a big problem because we know who the speakers are anyway and if someone who is not, enters the backstage to spam we can always kick them.

Problem Solving

Priority:

Fighting Burnout!

• Having more hosts other than Penguin (co-hosts)
• Having more people to help the guests in Discord
• Having more people to help the guests in Backstage

Accountability:

Set your role and availability!

https://www.notion.so/meta-game/Form-crews-roles-82b3cacfc0524afe9449518922673635

Guest No show/Stream Flow:

• Minimize silence
• @Scott Stevenson can go to cryptovoxels

Secondary Issues

Awkwards Transitions/Silence

• Elevator Music - Voice Meter Banana
• Use when transitioning from guest to guest

Views/Reach

• Lawnmower’s Suggestion (refreshing, adding a spam contest, etc.)
• Since everything is being recorded and can be re-used it may be a good idea to aim for promotion and reach after MF2, as a post-event shill raid.

Engagement

Clarity for Speakers

More People to Help

• Wat do with stream?
  • If all on youtube, write a better description with links (discord, mg itself, gitcoin)
• Where more to promote
• Remove discord chat from website?
• Where are things happening? Workshops?
• Filling in all the roles needed
  • Split from full days
  • Existing operators to write checklists/short playbooks