Add notes from last session

1 files changed, 59 insertions, 2 deletions

diff --git a/2021/meetings.org b/2021/meetings.org
index 3496e3df..8d7655f3 100644
--- a/2021/meetings.org
+++ b/2021/meetings.org
@@ -41,6 +41,8 @@
   - org-roam
   - Mediation project between MELPA and org-mode’s core: zaeph
   - Community
+  - Modernise the notes for our EmacsConf meetings
+  - Find a moment to talk with mplsCorwin about FH funding
 
 - EmacsConf
   - Subtitles/transcripts: sachac, bhavin192
@@ -60,6 +62,60 @@
   - Diversity outreach: gopar, sachac, zaeph, mplsCorwin
 
 * May 15, 2021 meeting
+- Next actions from last time
+  - People-based:
+    - zaeph:
+    - bandali:
+      - Listing the specs for the non-FH servers (very quick)
+        - Done!
+      - Wipe the private-repo
+        - Will be done shorty; although we might want to keep it around for working on WIP stuff
+
+- Check-ins:
+  - zaeph:
+    - Got his vaccine!
+  - bandali:
+    - Will get his vaccine in a couple of weeks
+  - sachac:
+    - Taking care of kiddo today.
+  - mplsCorwin:
+    - It’s been a while!
+    - Voluntereed for Worg maintenance.
+
+- bandali & zaeph: BBB update report
+  - bandali successfully managed to update our BBB instance on bbb (the server)
+    - The update was supposed to only include security stuff; somehow, something still managed to break
+    - Debian and Ubuntu usually are pretty strict about security updates not breaking anything; if manual intervention is required, they print a popup
+    - The explanation here might be that it’s coming from a 3rd-party provider, which probably has less polish
+    - The FSF’s BBB instance is running on two servers which are managed via ansible
+  - However, we had a problem with the echo server dying on us, and we only noticed when Emacs-SF needed to go live
+    - The fix was to reset nginx, since something had been updated
+  - Fix for the future:
+    - When we update the server, we need to check if everything is still working
+    - If we set up auto-updates on a cron, we might want to have it fire on Sundays so that an orgas can check if everything still works
+
+- Recordings from the FSF’s BBB
+  - zaeph downloaded the old recordings from the FSF’s server
+  - They’re stored on his server
+
+- Emacs-SF [2021-05-13 Thu]: Getting recording from FSF’s BBB
+  - Recording is not available on the [[https://testgreenlight.fsf.org/leo-hh9-v49][room]]
+  - bandali is going to check 
+
+- Podcast
+  - bandali started working on the website
+  - We can push the discussion to next week
+
+- EmacsConf Improvement Meeting
+  - Sending an email on [2021-06-05 Sat] (3 weeks from now) to share conclusions from our debriefs
+    - This would provide some guidance for the discussion, and give people a month of prep if they want to participate
+  - The announcement is nice and important, but we should provide details on the bulletpoints that we’d be talking about (with like 2-3 lines to give food-for-thought to the people)
+  - bandali is
+
+- Demantling the private repo
+  - bandali was thinking of wiping/shreding all the git history, and only keep the simple files going forward (i.e. without VCS)
+    - Typically, we don’t need to track most of the changes in those files.
+
 - Next actions
   - Project-based:
     - UG calendar:
@@ -77,6 +133,9 @@
       - 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
       - Think about the wording of the email we’d want to send on [2021-06-05 Sat]
+        - 2-3 lines per axes of work
+      - From ERG:
+        - We might want to send a report with what we’ve done with regards to the comments that were made at the end of the previous edition
     - Misc:
       - Look into GLT21 to see if they have specifications/doc for their streaming
       - We might want to discuss the podcast during the next session
@@ -87,8 +146,6 @@
           - admin@emacsnyc.org (goes to both Eric & Zach)
       - Do the same with Emacs ATX?
       - Do the same with M-x Research
-      - Modernise our notes (org-roam?  org-agenda?)
-        - Isolate different meetings
     - bandali:
       - Check if there is anything important on live0 that would need archiving (besides the raw EmacsConf2020 ಠ_ಠ)
       - Listing the specs for the non-FH servers (very quick)