Skip to content

Commit 24dbe4a

Browse files
authored
Add files via upload
1 parent 1b6f832 commit 24dbe4a

File tree

1 file changed

+100
-0
lines changed

1 file changed

+100
-0
lines changed

docs/README.md

Lines changed: 100 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,100 @@
1+
# This will mostly be internal, but sharing as a resource to everyone on the internet and to our future-selves for the next event.
2+
3+
Online conference checklist
4+
5+
## BEFORE THE EVENT
6+
```markdown
7+
*[ ] Setup web with info about at least: "WHAT", "WHEN", "WHERE" (youtube/twich), "HOW" (ctf, r2wars)
8+
Resources, free images: https://pixabay.com , https://www.pexels.com
9+
*[ ] Create tg (or other communication channel) for ctf, r2wars and any other competition
10+
*[ ] Prepare logo for the conf and make it available in svg format in the web/shared cloud
11+
12+
*[ ] Open CFP (3-4) months before r2con ; ask humans submitting papers for day/hour of prefference for their talk (try to make it timezone friendly)
13+
INFO TO COLLECT FROM SUBMISSIONS
14+
- Title, type (talk 30 min, talk 45 min, training 2/4/8 hours), description, notes, aditional speaker, reference links (optional)
15+
- Public display name, twitter handle/personal webpage/GitHub (we will use this for tweets and promotion), name, bio
16+
Lessons learned: people like to talk but the webpage space is finite, set up a character max for bio! e.g. (max 400 chars)
17+
18+
SPEAKERS
19+
*[ ] Send ack mail to humans that submited a paper/walktrhough workshop
20+
*[ ] Review CFP submissions, meet, decide which ones pass and communicate with speaker/trainer via mail
21+
22+
MUSICIANS
23+
*[ ] Create communication channel & request music artists info: bio, personal web, instagram/twitter + bandcamp/soundcloud/mixcloud/spotify
24+
*[ ] Set up promotion poster for chiptune/music artists to tweet and send instagram posts
25+
*[ ] Prepare twich overlay. There's plenty of templates on the internet, with pre-defined aspect-ratios: play around, test.
26+
27+
CTF / R2WARS / HACKATHON / other competitions
28+
*[ ] Brainstorm
29+
*[ ] Meet, test and decide based on previous editions
30+
Lessons learned: this needs preparation meetings too, even if there's previous experience.
31+
Request specific info for the conf web: game instructions, when does it start, how does registration work, who wins, what are the prices...
32+
33+
*[ ] Setup info on the web: "WHO"
34+
35+
*[ ] Create telegram channel (or other: irc, signal, discord, slack ...) for speakers to be aligned
36+
*[ ] Try to adjust the talks to the speaker preference to make the event as timezone friendly as possible
37+
*[ ] Draft the schedule and check in telegram if the speakers can adjust (changes may be required as time goes by, so be flexible on this one)
38+
*[ ] Set a deadline for the schedule to be set up.
39+
*[ ] Publish the schedule on the web/twitter/telegram/irc ...
40+
41+
*[ ] Prepare logo miniature & setup slides template "Slides > Edit > Master" (https://support.google.com/docs/answer/6386827?co=GENIE.Platform%3DDesktop&hl=en)
42+
*[ ] Send slides template to speakers/trainers/competition organizers
43+
*[ ] "presenter tools with Q&A" + "gslides laser tool" live demo in a meet, with all humans that will be presenting at the event
44+
Resources: https://www.blog.google/products/docs/slidesqa https://youtu.be/weooOudyDuc?t=95
45+
46+
*[ ] Setup & test OBS (here comes the good old fun)
47+
OBS works in Win/OSx/Linux. OBS it's a universe in itself, get familiar with it:
48+
*[ ] Setup OBS scenes https://obsproject.com/forum/resources
49+
*[ ] Setup OBS sources
50+
*[ ] OBS studio mode allows transitioning between scenes
51+
Resources: https://www.youtube.com/watch?v=AA5uMiSk2MQ&ab_channel=CreatorFundamentals
52+
*[ ] Prepare lightweight mp4/gif to have it handly between talks, during breaks, or in case of tech issues from speakers/delay between talks
53+
*[ ] OBS guide for electro-music artists https://www.jeremydeprisco.net/blog/cosmic-stream-fest
54+
To do: test streaming to several platforms at once https://restream.io
55+
56+
*[ ] Meet with all humans that will present at least twice (timezone friendly) before the event to
57+
*[ ] Test everyones internet connection / audio setup / video setup
58+
*[ ] Make sure people can share the whole desktop when presenting screen in google meet
59+
*[ ] Take notes of the meeting, answer questions, allow brainstorm time.
60+
*[ ] Send a recap mail with all that was agreed during the meet!
61+
*[ ] In the mail include clear instructions "how to proceed during the conference"
62+
63+
*[ ] Send mail/pdf with clear instructions on how the event will take place and what is expected from the speakers/trainers
64+
*[ ] Set deadline for speakers to send the slides in pdf format, to be rewieved before the online event
65+
Lessons learned: do not collect slides in telegram/mail, allow people to send a PR to GitHub (otherwise you will be pinged and receive incremental versions with new changes)
66+
*[ ] Set deadline for pre-recorded talks. Allowing people to pre-record their talks is a good idea (people with low quality internet, humans in different timezones ...)
67+
Lessons learned: be flexible on talk lenght! Pressuring people to compress their talk in 30 mins if there's lots of content is not a good idea.
68+
*[] Prepare at least one tweet per talk/workshop to have it handly for copy/paste during the event to be sent BEFORE/DURING the talk
69+
```
70+
71+
## DURING THE EVENT
72+
```markdown
73+
*[ ] Make sure communication is effective: twitter hashtags, regularly check attendees telegram, youtube chat, email
74+
*[ ] Send pre-cooked tweets for each talk with the youtube url (live streaming) and the slides URL for the audience to send questions
75+
*[ ] Send the slides url for audience questions in tg attendees channel, announcements channel, youtube chat, twitter
76+
*[ ] Have a backup setup/plan in case internet breaks down or OBS makes the computer too hot
77+
```
78+
## AFTER THE EVENT
79+
```markdown
80+
*[ ] Keep the communication channels open (discord, irc ...)
81+
*[ ] Send a feedback form to listen and learn from the people that was at the other end of the screen!!
82+
If you're the OBS master in charge of the event, it's likely that you are not aware of possible glitches/mistakes that happened life in the video streamed to youtube/twich
83+
To do: Open a suggestion box of some kind
84+
```
85+
86+
## TIPS
87+
- Test how to stream to youtube "scheduled events" before going live
88+
- Mastering your skills in OBS takes practice, streaming keys can be saved with custom names in OBS, that's very useful!
89+
- Allocating some holiday/free of work days, a month before a 4 day event may be a good idea.
90+
Lessons learned: Balance it out, you also need real holidays!
91+
- Be organized: set up meetings with a clear title in gcalendar, add the meeting doc in the calendar event so everyone can edit it BEFORE the meeting
92+
- Use document versioning on google drive and backup docs/images/resources
93+
- For pre-recorded videos, people can upload it to their youtube account and set it as unlisted.
94+
Lessons learned: youtube videos set as private are only available to the uploader, request people to set videos as "unlisted" so people with the URL has access.
95+
- Set up wesite DNS redirects (youtube, ctf, competitions ...) at least 1 week in advance, no need to add extra pressure to the event.
96+
- Use telegram anonymous polls in groups to set up meeting day/hour, to ask for ideas, to get feedback...
97+
- Use tweetdeck for effective communication, e.g. set up scheduled tweets for each day a few hours BEFORE the event with the schedule so people know when it starts
98+
- There's other humans highly experienced in online events, learn from them:
99+
https://github.com/vmware-tanzu/tgik/tree/master/documentation#scheduling-on-youtube
100+
- It's nice to have a backup for tech issues in talks, you may want to open a "lightning talk" slot when opening the CFP

0 commit comments

Comments
 (0)