diff options
Diffstat (limited to '')
| -rw-r--r-- | 2020/meetings.org | 74 |
1 files changed, 70 insertions, 4 deletions
diff --git a/2020/meetings.org b/2020/meetings.org index 2dbd8fd3..e1af50e9 100644 --- a/2020/meetings.org +++ b/2020/meetings.org @@ -25,10 +25,76 @@ * January 21, 2021 meeting -- Updates - - Sacha: - - Added transcript for 08 and edited subtitles for 21; only 03-questions and the opening/closing remarks remaining for day 1 - +- Updates: + - Sacha: one more talk left to transcribe for day 1, hooray! + Everything else has been edited. Next step for day 1 is to edit + the subtitles into transcripts and make them available. Also want + to check if ableplayer passes LibreJS, since that can give us + clickable transcripts; will include text transcript anyway for + non-JS. + - zaeph: Emacs Research Group wants to meet daily + - bandali: A little tired because of work; but good progress is + being made (yay!). Some progress done on the podcast. + - corwin: mental health improving; looking forward to getting back + to the swing of things :) +- Next EmacsConf: Calendar? + - We could stick to the same period as 2020's edition (i.e., + mid-November to mid-December) + - CFP? + - start earlier: accomidated anticipated higher + - First entire week of July might be a good time: it'd give us 4 + months before the actual conference + - Office hours + - Could be used for the outreach part of the CFP + - Could also keep people excited about EmacsConf + - On the format + - A regular timeslot where people can join + - We ask them whether we could use a recording of the session to + build some hype for the EmacsConf + - We can also have a private moment with them to address some of + the possible problems with their talk/topic + - Short-ish and regular works best, probably + - Let's work on this during February, and let's aim for a first + session in March + - if there are not presentations we can record and share we + could use clips from recent orginizer meetings; we could close + meetings with statements intended for this use. +- On having multiple tracks for the next EmacsConf, either + simultaneous or single-threaded + - Three tracks based on levels of mastery, e.g.: + - Beginners + - Pro-users + - Package developers + - Last year, we had de-facto tracks, or recurring topics like music, + academic research, SVG-graphics, games, typography/themes, + free-software philosophy, etc. + - We could use this info for the *outreach program*: 'We'd love to + have people come talk to us about music' +- Overhauling the graphics for the conferenc + - Posters? + - Scenes in OBS + - Custom dashboard.el ? +- Figuring out the roles for the next EmacsConf + - Fleshing out roles for everyone in advance (so that we're not + figuring it out one week prior) and along with this any private + comms to faciliate (e.g. iff voice-over and cuts are different + roles). +- Diversity discussions + - Taking inspiration from the GNU Kind Communication Guidelines +- On changing the time for the weekly meeting + - Corwin is happy to keep the same time because it'll motivate him + to wake up early on Saturdays + - We could have a monthly session which takes place on a weekday to + try to get more people on board (David O'Toole, David Bremner, + Karl Voit, etc.) + +- Ongoing projects for February: + - FSF Fiscal sponsorship (Leo) + - Office hours roadmap (Leo) + + + + * January 14, 2021 meeting - Updates: |