diff options
Diffstat (limited to '2021/meetings.org')
| -rw-r--r-- | 2021/meetings.org | 144 |
1 files changed, 143 insertions, 1 deletions
diff --git a/2021/meetings.org b/2021/meetings.org index aef24ccc..3f874819 100644 --- a/2021/meetings.org +++ b/2021/meetings.org @@ -49,6 +49,7 @@ - Set of methods for clipping, publishing, etc. - Coming up with a way to coordinate meetings with *all* the organisers of the EmacsConf (rather than the core subset) - Coming up with a calendar for the next edition + - Decide whether the live-version of the EmacsConf 2020 can be axed by [2021-06-12 Sat] - EmacsVerse - Vet Mailman and exim instance for usergroups: bandali @@ -58,6 +59,41 @@ - mplsCorwin's livestreaming project, working on trimming - Diversity outreach: gopar, sachac, zaeph, mplsCorwin +* May 15, 2021 meeting +- Next actions + - Project-based: + - UG calendar: + - Help sachac figure out an updating workflow for the ICS feed + - bbb: + - BBB experimentations: + - See if increasing the RAM results in less CPU usage + - Gauge how much the number of present users affect the resources + - 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 + - Think about the wording of the email we’d want to send on [2021-06-05 Sat] + - 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 + - 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) + - Organisers to content: + - 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) + - Wipe the private-repo + * May 8, 2021 meeting - Next actions from last session @@ -69,7 +105,7 @@ - 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 + - 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: @@ -90,6 +126,112 @@ - Podcast: - Think about announcing the podcast +- Check-in: + - bandali: + - Feeling good! + - zaeph: + - Feeling good! + - sachac: + - Feeling good! + +- bandali: On our infrastructure + - Notes were taken in our private repo + - front0 + - If we get more money, we might want to move stuff over to other servers because we’re making heavy usage of front0 + - Mail servers + - bandali updated the exim version with security fixes + - live0 + - Used as the primary icecast stream server + - We’re running out of space + - bandali might be fetching some of the videos and move them locally or to another server (e.g. FH’s) to make some room + - ‘It makes sense to remove the previous one + - bbb + - As bandali was ssh’ing into the bbb servers, there were lots of update available + - bandali is going to update the server now, and set up a routine for security updates + - On publishing our infra + - Maybe we could make some of the info on our infra public (like the capabilities of the servers, or where we are hosting what) + +- zaeph gushed about the lispy stuff that he had been writing this week + +- Podcast: Do we need to chat about it today? + - It might be interesting to discuss when to announce the podcast + - We’re waiting on the greenlight from gopar since some stuff remains to be done + - bandali: The website also needs to be set up + +- On the BBB server, the well-named ‘bbb’ + - We did get our update from 4GB to 8GB (yay!) + - Someone from FH (not mplsCorwin) did it, although it was also nudged by mplsCorwin; in short, thanks everyone! + +- On Emacs NYC + - sachac attended + - They’re interested in testing our BBB platform + - zaeph will take care of this (alongside ATX and M-x Research) + - They’re also interested in special interest groups, particularly: + - Org+gtd + - Beginner-oriented UG + - bandali also mentioned emsig for Emacs multimedia stuff + - We might want to focus on this interest-based UG in the summer, especially as geo-based UG revert to in-person meetings + - Another path of work could be to figure out how to stream the in-person meetings + - bandali: ‘Maybe we could think of online-events as EmacsConf events with themes, like gaming, GTD, music, multimedia’ + - This could be a discussion to have during the public meeting we’ll be having soon + +- EmacsConf Public-Planning meeting (formerly known as the ‘Emacs Improvement Meeting’) + - zaeph is going on holiday for most of June, and it might be hard to squeeze it in early-June or in the 2nd half of April + - As a result, let’s aim to have it in the first week of July; but we need to bear in mind that a lot of people might be on holiday) + - That would also entail having 6 different actions to do in July: + - Have the improvement meeting + - Make adjustments according to the meeting + - Have a 2nd meeting where we share our adjustments + - Make a 2nd round of adjustments + - Prepare for the CFP + - Announce the CFP (by July 19) + - We should probably start this discussion asynchronously on our mailing lists so that people may prepare for the meetings + - It would show that we care about people preparing for this meeting + - Tentative calendar: + | Send email announcing the public event | [2021-06-05 Sat] | + | Public event | [2021-07-03 Sat] | + | Potential 2nd public event | [2021-07-10 Sat] | + | CFP + Announcement for office hours | [2021-07-19 Mon] | + - Observations: + - We announce the event a month ahead + - We have a week after the first public event to implement changes + - The 2nd public event will only be warranted if we need to make fundamental changes to our approach + - We have a week after the 2nd public event and before the CFP to make final adjustments + +- Next actions + - Project-based: + - UG calendar: + - Help sachac figure out an updating workflow for the ICS feed + - bbb: + - BBB experimentations: + - See if increasing the RAM results in less CPU usage + - Gauge how much the number of present users affect the resources + - 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 + - Think about the wording of the email we’d want to send on [2021-06-05 Sat] + - 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 + - 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) + - Organisers to content: + - 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) + - Wipe the private-repo + * May 1, 2021 meeting - Check-in: - bandali: |