summaryrefslogtreecommitdiffstats
path: root/2021/meetings.org
diff options
context:
space:
mode:
Diffstat (limited to '2021/meetings.org')
-rw-r--r--2021/meetings.org56
1 files changed, 53 insertions, 3 deletions
diff --git a/2021/meetings.org b/2021/meetings.org
index 0bea735..aef24cc 100644
--- a/2021/meetings.org
+++ b/2021/meetings.org
@@ -58,7 +58,39 @@
- mplsCorwin's livestreaming project, working on trimming
- Diversity outreach: gopar, sachac, zaeph, mplsCorwin
-* May 1st, 2021 meeting
+* May 8, 2021 meeting
+
+- Next actions from last session
+ - 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?
+ - EmacsConf improvement meeting
+ - Think about potential topics of improvements (diversity, accessibility, tech, outreach, etc.)
+ - Look for questions to submit to the panel/public with regards to diversity, accessibility, or any topic we see fit
+ - 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:
+ - admin@emacsnyc.org (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
+
+* May 1, 2021 meeting
- Check-in:
- bandali:
- Since the peak 2 weeks ago, things have been getting better
@@ -129,8 +161,23 @@
- 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
- -
+ - After doing a 5-10’ presentation of all those points, do we want to ask people questions, or are we just happy to let the discussion be free?
+ - We want to appear as open as possible; as such, we might want to make it clear that the plan that we have is based on the previous editions of EmacsConf, but that we are quite willing to adapt it based on the participants’s inputs
+ - We don’t need to mention that we should remain civil, unless there’s a particularly egregious offender
+ - Questions we could ask:
+ - ‘What’s working elsewhere? Do you have examples of conferences doing well with regards to these issues?’
+ - Let’s come up with more questions for next time
+ - ----------------------------------------
+ - Should this discussion be a subset of a general EmacsConf improvement meeting
+ - If we are to engulf the diversity meeting into another one, we should nevertheless mention that diversity & accessibility should be essential talk-points
+ - We don’t have to limit ourselves to just this one meeting
+ - We could also announce the outreach program, and start with the office hours not too long after the meeting
+ - Do we want to make this meeting public?
+ - We don’t necessarily stream it; we could just do it in a BBB room
+ - This way, we can ask participants if they’re okay with us publishing their recording
+
+- Podcast
+ - bandali & gopar had little time to work on the podcast; we’ll talk more about it next week
- Next actions
- Project-based:
@@ -141,6 +188,9 @@
- 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?
+ - EmacsConf improvement meeting
+ - Think about potential topics of improvements (diversity, accessibility, tech, outreach, etc.)
+ - Look for questions to submit to the panel/public with regards to diversity, accessibility, or any topic we see fit
- Misc:
- Look into GLT21 to see if they have specifications/doc for their streaming setup
- People-based