diff options
authorLeo Vivier <>2021-05-01 17:37:49 +0200
committerLeo Vivier <>2021-05-01 17:37:49 +0200
commit145e45a765b31a9dafa6e57b650bb072fd414357 (patch)
parentb7d43ee71bbfdc451b34d2d7ab588338b971883e (diff)
Push notes from last session
1 files changed, 101 insertions, 0 deletions
diff --git a/2021/ b/2021/
index 1feb67f..0bea735 100644
--- a/2021/
+++ b/2021/
@@ -58,6 +58,107 @@
- mplsCorwin's livestreaming project, working on trimming
- Diversity outreach: gopar, sachac, zaeph, mplsCorwin
+* May 1st, 2021 meeting
+- Check-in:
+ - bandali:
+ - Since the peak 2 weeks ago, things have been getting better
+ - Has been able to go back to GNU Savannah, and was happy about it
+ - sachac:
+ - Doing chores in the background
+ - ‘learning steno, infiltrating steno community (interestingly, it's majority-female), wrote plover-websocket-el for controlling steno software from Emacs :)’
+ - zaeph:
+ - Is excited about sachac’s work on steno!
+ - Did build emacs’s main(/master)
+- Building Emacs’s main(/master) & native compilations
+ - Useful commands for cleaning the repository (in case of compilation problems with byte-/native-compiled files
+ #+begin_src sh
+ git clean -xdf
+ make distclean
+ #+end_src
+- Retrieving recordings from the FSF
+ - Low-priority, but it’d be nice if we could do it before the end of May.
+ - bandali got a link from the FSF team.
+ - The link that we got allows us.
+ - sachac: ‘The webm links follow a consistent pattern based on the meetingId’
+- Next actions from last time
+ - People-based:
+ - sachac:
+ - Check if you have access to the bbb server: Done!
+- Diversity (& potentially Accessibility) meeting:
+ - Think about people to invite to the meeting.
+ - Check if they’re available for [2021-05-15 Sat]
+ - Assess whether we need to have two days to cover more people.
+ - This might require some outreach prior to the diversity meeting
+ - ----------------------------------------
+ - It might be best for us to thing of this diversity meeting as something to organise (like the EmacsConf)
+ - We’d be calling it for that meeting, but we would not be the *centre* of it; we’d merely be presenting our conclusions from last year, and the outreach program that we had in mind
+ - Do we want to put forward something and bias the discussion? It would not necessarily be /imposing/ anything (it’s our conference, after all)
+ - If we are to present, it should be fairly short (5-10’) to keep it as a /discussion/
+ - ‘We’re not going to auto-magically solve every-problem; but we want to give our ideas to people, and make sure that people agree/disagree with what we’ve done
+ - How to deal with controversial figures
+ - The ‘RMS question’
+ - ‘We collectively had this thought or idea that we could have these people as long as, first of all, their presentations and discussions are centred around Emacs (and not something completely off-topic); and we also have a set of guidelines for conduct and such that, if any problem was to arise, we could point to that.’
+ - Bottom-line: We’ve already implemented safe-checks for this
+ - If someone is a horrible person that has done horrible thing, we wouldn’t be excited about having them along; but as far as we are concerned
+ - We tried to rôle-play possible answers that could be given to our reactions with RMS, and we can see that it’ll take a lot of preparation
+ - Putting people on the spot with questions like the one zaeph had at the end of his first presentation (with regards to the impact of his ethnicity/gender on his developer experience): What could we do?
+ - We don’t want the speakers to be dismissive of it because it shows either a lack of importance
+ - We said during the debrief that it’d be something to approach in the speaker-prep
+ - As a temporary measure, /delaying/ is perfectly reasonable response
+ - Answering later helps keeping things calm
+ - [IMPORTANT] Conclusions on dealing with controversial figures or loaded questions
+ - Teaching speakers to /defer/ is probably the best thing we can do
+ - We can also implement a safe-word (or safe-action) for speakers to communicate unease
+ - ‘Hey $orga, what do you think about this?’
+ - It’s a signal for orgas to interpret; they could be using this sentence in non-stressful situations, but it’ll be up to our discretion to see what to do.
+ - On our ends (the orgas), we can prepare a little more for loaded questions (especially questions of social-justice) so as to assist the speakers and take the onus for addressing the question with the persons asking the questions
+ - Orgas can also add nudges in the Etherpad (if we use it again this year)
+- On a related note, with regards to fielding questions to speakers (instead of having them read the questions on their end)
+ - We’re not sure if we want to do it all the time; but if we’re comfortable with it, we may
+ - We could try it to make it more conversational with the speakers
+ - We could set up a team of orgas with one orga introducing the person (potentially the pre-checker), another orga to ask the question, and yet another orga to prepare the questions on the Etherpad (adding hedges for loaded questions)
+ - With regard to pronouncing the names properly
+ - We can ask them during the speaker-prep (ahead of the conference)
+ - We can ask them during the pre-check
+ - During the pre-checks, orgas should ask speakers for their names, how to pronounce them, and the pronouns that they use.
+ - We need to fully internalise the asking/giving of pronouns at every step of the way for the conference (tech-checks, pre-checks, beginning of conf for orgas, etc.)
+ - We can do this as a nudge for people, as in, we’re not ‘forcing’ people to give their pronouns, but we are encouraging them (so, optional)
+ - We should also standardise the pronunciation of names (via IPA or via English vocalisation) as a low priority
+ - ----------------------------------------
+ - After doing a 5-10’ presentation of all those points, do we want to ask people questions, or are we just happy to
+ -
+- Next actions
+ - Project-based:
+ - bbb:
+ - See if increasing the RAM results in less CPU usage
+ - Working with the swap
+ - Decreasing the swapiness of the kernel might help
+ - Test RW speed (elsewhere than ~/tmp/~)
+ - Check if we can change the ffmpeg prioritisation for BBB (so as to get recordings out sooner, or to manage them ourselves)
+ - Does bbb spawn a ffmpeg process that we can investigate?
+ - Misc:
+ - Look into GLT21 to see if they have specifications/doc for their streaming setup
+ - People-based
+ - zaeph:
+ - Email Emacs NYC (and Cc sachac and bandali) to ask them if they’d be interested in hosting their sessions on our BBB instance (on FH)
+ - Next session: [2021-05-03 Mon]
+ - Organisers to content:
+ - (goes to both Eric & Zach)
+ - Do the same with Emacs ATX?
+ - Next session: [2021-05-05 Wed]
+ - Modernise our notes (org-roam? org-agenda?)
+ - Isolate different meetings
+ - bandali:
+ - Set up the vm01 server
+ - Listing the specs for the non-FH servers
+ - Podcast:
+ - Think about announcing the podcast
* April 24, 2021 meeting
- Tentative agenda
- Diversity outreach