summaryrefslogtreecommitdiffstats
path: root/2020/meetings.md
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2021-01-23 00:38:03 -0500
committerSacha Chua <sacha@sachachua.com>2021-01-23 00:38:03 -0500
commitdb77cf5d561ad64d17cc43da378c261169169f0e (patch)
tree14834291f35723cb01986fc5a25d4a9166f2205f /2020/meetings.md
parent406e10b8e8ad8635c272fc52bdb9b4657d9487aa (diff)
downloademacsconf-wiki-db77cf5d561ad64d17cc43da378c261169169f0e.tar.xz
emacsconf-wiki-db77cf5d561ad64d17cc43da378c261169169f0e.zip
Update
Diffstat (limited to '2020/meetings.md')
-rw-r--r--2020/meetings.md77
1 files changed, 73 insertions, 4 deletions
diff --git a/2020/meetings.md b/2020/meetings.md
index 55782ce7..52105d12 100644
--- a/2020/meetings.md
+++ b/2020/meetings.md
@@ -14,7 +14,51 @@
- Writing about Emacs: zaeph
-# January 7, 2020 meeting
+# 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
+
+
+# January 14, 2021 meeting
+
+- Updates:
+ - Sacha:
+ - More subtitles edited (bhavin192 is helping too). Almost done
+ with day 1 except for opening/closing remarks and manual transcriptions for 03-questions and 08
+ - switched to using emacsnews Reddit account
+ - scheduled tweets from @sachac about upcoming Emacs events - do you want these mirrored to @emacsconf or something?
+ - no new events aside from the ones already on the calendar
+ - bandali: recorded first episode of Emacs Weekly, skipped the news component and just had an interview about EmacsConf
+ - next:
+ - mix audio together and edit it
+ - plan to have several buffer episodes before releasing, maybe beginning of February
+ - can put together separate segments
+ - news might be doable with less prep
+ - can do solo episodes
+ - maybe community hosts, too?
+ - nudge from Sacha to transcribe or have show notes if possible =)
+ - gopar doesn't have a laptop at the moment
+ - which parts of your config might be good to contribute to core?
+ questions to nudge people to contribute to core/packages
+ - This question coudl also be used in workshops settings with a sense of chronology: 1. publish it online, 2. merge it to core?
+- Q for mplsCorwin: would you like to transcribe 03-questions and 08, or shall I go ahead and do them? - sachac
+- Q for bandali: is the emacsnews Reddit thing handy for you? It's okay if you're still experimenting.
+ - not tested yet
+- Testing quick collaboration
+ - Testing tmate so that other people can edit the meeting minutes easily
+ - Test? it is working!
+ - Here I am in tmate and emacsclient. Each person can have their own emacsclient tab.
+- pat selves on back for getting stuff done, yay
+- Diversity workshop: It'd be nice to organise a 2h session where we discuss every problem that arised in the last conference, and pre-empt those that might arise for the next editions
+ - Using the word 'open source'
+ - Lack of diversity in the presentations (CFP?)
+- Next steps:
+ - sachac: follow up with mplsCorwin or transcribe 03-questions, 08; then all the day 1 talks will be done
+
+
+# January 7, 2021 meeting
- Checking in:
- bandali, zaeph, gopar, sachac, dto
@@ -30,6 +74,15 @@
- bandali
- met with organizers of EmacsNYC. They were curious about BBB and Jitsi, streaming, IRC web client
- met with gopar last night re: podcast
+ - will work on a blog post about the technical setup
+ - someone wanted to set up a meetup in Mexico, too, so maybe we can make an updated starting-a-meetup guide (<https://harryrschwartz.com/2015/09/14/starting-an-emacs-meetup.html>)
+ - how to find people and advertise
+ - reddit.com/r/emacs
+ - Emacs News
+ - <https://www.emacswiki.org/emacs/Usergroups>
+ - how to stream and record
+ - what it might be like if there are no presentations (don't worry! hang out, share cool stuff, figure things out together, flip through Emacs News)
+ - sharing afterwards
- CRDT: see BBB chat if you want to try it
- dto:
- tutorial; (also, SystemCrafters just livestreamed an Emacs Lisp tutorial too)
@@ -40,13 +93,29 @@
- BBB has breakout rooms, might be worth looking into if it scales up a lot; Jitsi can have multiple people sharing screens at the same time;
- EmacsNYC said Jitsi is okay for the 20-30 people they've seen so far; EmacsBerlin said the same too (I think they self-host; want to see how they're doing it?). Sounds like it's much better now than it was last year
- dto will figure it out and write things up =)
+ - one-on-one tutorial was nice; finger memory for how to type some of these Lisp expressions
+ - it's better to have that interactivity, I think, since there are plenty of lecture-type resources on the Net
+ - one-on-one is fine, and then you can scale up (1-on-2, etc.) as you become more comfortable with it and see what can help you scale (ex: having them SSH into a shared server with emacsclients and then being able to quickly flip through their buffers so that you can peek over their shoulder or quickly show something?)
+ - gopar: upcoming podcast recording re: EmacsConf experience
+ - figuring out name
+ - planning to have a little buffer
+ - Hey, do you want to blend that into the Emacs Lisp / Emacs tutorial/workshop idea? Whenever you don't have any content, you can teach people a little more
+
+ -
- bhavin192: Mailing list for meetups (some common prefix or something similar).
+ - **let's remember to discuss this and the next point** =)
- bhavin192: Update to Code of Conduct (I was hoping to use the same text or page for Emacs APAC meetup)
- - gopar: upcoming podcast recording re: EmacsConf experience
- -
+ - zaeph: figuring out collaborating via Org Mode
+ - per-project pages make sense if you think about it from the web publishing point of view
+ - bandali: can be a different wiki if you want
+ - zaeph is a little intimidated by the idea of working with the garage door open
+ - there is already a private organizer wiki, so we can use that to incubate things if you want to collaboratively work on notes and stuff
+ - also totally okay to work on things individually and not collectively if you want, and we don't have to figure out workflows that work for everyone or a name that covers everything; sounding official increases expectations and may cause problems
+ -
+ - Next:
-# January 2, 2020 meeting
+# January 2, 2021 meeting
- Conversations
- mplsCorwin: FOSSHost: okay to experiment with being a CDN, will