You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This year, there are lots of new folks (including myself 👋 ) helping to organise this devroom. As we divide ourselves into different roles, we thought it would be helpful to create check-lists for each role, to help keep track of what folks need to do for each role. Maybe we can add these lists to the repository? So far in our organising pad, we've come up with the following tasks:
These roles are split between the door team (🚪) and stage team (💃 ). Within each group, there is a lot of room to help each other with tasks.
Start of Day Welcome (not a set role - does the 1st moderator does this?):
Welcome + introducing room
Introducing devroom team (everyone wave! 👋 )
Sharing Code of Conduct ('reach out to any members of the devroom team - everyone is wearing yellow lanyards. X & X are our points of contact)
Flagging links, posters, qr codes throughout the room (and online event - happening the following Saturday!)
Flagging for speakers about timing ('X person will hold up a sign when you have 1 min, 30 sec?')
Moderator 💃 :
Responsible for blocks of 2.5 hour sessions
Introduce speaker and title of talk
Supplying computer for presentation (if needed)
Finding/flagging next speaker (reminder: don't tap your microphone!)
Thanking speaker (after talk)
Asking for questions from the audience (reminder: lightning talks have no questions, repeat questions into the microphone for the livestream)
Backup 💃 :
Grabbing microphones for questions
Back-up for social media role
Helping to add mics to speaker (d
Social media 💃 :
Overlaps with backup
Posting between mastodon and twitter
Takes pictures
Tweeting about talks and retweet/retoot other people's
Camera tech 💃 :
Responsible for starting and ending recording for talks
Starting timer of talks
Holding up timing for speakers (1min, 30sec signs?)
Helping with connecting computer, mic speaker
Gatekeeper (2 for each session) 🚪: Standing by doors to stop people from coming in and out during talk times (to not disrupt speakers)
Feeder: Grabbing food and drinks for organising team (usually during afternoon)
The text was updated successfully, but these errors were encountered:
Opening chat: welcome! (maybe a bit about the devroom? didn't do this), about program (mix of lightning talks and longer talks - mentioned nothing about ), code of conduct, link to eve meeting information, qr code for info, best practices for being in the room, introducing organisers, blue shirt people are the gatekeepers, reminder about how to move around the room
Utilise the sign to ask folks to repeat their questions (stay close to the screen/stage)
Speaker shares/repeats
Round of applause
different styles of moderation (i like the second!)
introducing them for them (saying name & title) vs people introduce themselves
we help to choose questions vs they choose their own questions
difficult for people to remember to repeat their question – maybe someone is always staying in front of the stage?
This year, there are lots of new folks (including myself 👋 ) helping to organise this devroom. As we divide ourselves into different roles, we thought it would be helpful to create check-lists for each role, to help keep track of what folks need to do for each role. Maybe we can add these lists to the repository? So far in our organising pad, we've come up with the following tasks:
These roles are split between the door team (🚪) and stage team (💃 ). Within each group, there is a lot of room to help each other with tasks.
Start of Day Welcome (not a set role - does the 1st moderator does this?):
Moderator 💃 :
Backup 💃 :
Social media 💃 :
Camera tech 💃 :
Gatekeeper (2 for each session) 🚪: Standing by doors to stop people from coming in and out during talk times (to not disrupt speakers)
Feeder: Grabbing food and drinks for organising team (usually during afternoon)
The text was updated successfully, but these errors were encountered: