summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLeo Vivier <zaeph@zaeph.net>2021-12-11 18:16:06 +0100
committerLeo Vivier <zaeph@zaeph.net>2021-12-11 18:16:06 +0100
commitfa0bcb1e1f11799dfd20ee6f8e02dc31dc5566f5 (patch)
tree967a93209dc5c1e66574f9538f9d776f77860dd5
parentf071f1d862ded2b7b64be63ec8da80c346a9b446 (diff)
downloademacsconf-wiki-fa0bcb1e1f11799dfd20ee6f8e02dc31dc5566f5.tar.xz
emacsconf-wiki-fa0bcb1e1f11799dfd20ee6f8e02dc31dc5566f5.zip
Add tentative summary of decisions
Diffstat (limited to '')
-rw-r--r--2021/meetings.org15
1 files changed, 14 insertions, 1 deletions
diff --git a/2021/meetings.org b/2021/meetings.org
index d96d11f3..0a29043f 100644
--- a/2021/meetings.org
+++ b/2021/meetings.org
@@ -123,6 +123,8 @@
- Time feels weird; it’s been both short and long since we last saw one another
- bandali
+- zaeph: We’ve talked about a lot of interesting stuff, but I couldn’t make significant points *and* take notes at the same time. The few haphazard notes I’ve written are in the next block.
+#+begin_quote
- Async vs live meeting
- How do we keep all the organizers up to speed on what sachac and zaeph are working quasi-synchronously via IRC?
- bandali: Could we have a weekly email keeping everyone up to speed?
@@ -133,8 +135,19 @@
- corwin: Maybe it’s not an actual problem right now; yes, better communication would be better, but it can probably wait.
- Solutions:
- Splitting up #emacsconf-org into *thematic* topics like #emacsconf-infra, #emacsconf-post
+#+end_quote
-- [zaeph: We’ve talked about a lot of interesting stuff, but I couldn’t make significant points *and* take notes at the same time. I’ll try to fix this later when I get the chance.]
+- Summary of changes, written hastily so as to not forget
+ - As a project grows, it becomes harder and harder for organisers to one-person-army everything; specialisation is a good solution.
+ - Core-organisers are in charge of the project and are the guarantor of its philosophy; we should keep an initial distinction between volunteers and core-organisers so as to maintain governance.
+ - Core-organisers should move away from the “I need to keep up with everything”, FOMO-like mentality; instead, they should specialise on *themes* that they enjoy working on and were they can satisfactorily handle the work-load.
+ - Volunteers are piped to relevant themes/projects relative to their interest; they become the soft-responsibility of the core-organiser in charge of the theme.
+ - Core-organisers manage their theme with as much flexibility as they want; the only important part is about keeping other core-organisers in the loop (potential solutions: weekly blurb for each theme written by the responsible core-organisers)
+ - If a core-organiser wants to participate in another theme than the one they’re responsible for, it’s completely fine.
+ - Weekly core-organisers meetings are phased out in favour of a new regular format where the core-organisers can hang out, check-in and discuss weekly blurbs if need be (≈ 20 min), and then have flexible sessions which can either be casual discussions or longer-term planning that would require brain-storming (like creating a new theme/project, e.g. “how to have another in-person EmacsConf?”).
+ - IRC has been instrumental to good communication for EmacsConf 2020 & 2021, and it’s only recently proved to be a bit of a burden with the line-backlogs. Splitting the channels according to themes might leverage that issue.
+ - Only the core-organisers in charge of a particular theme would be expected to keep track of the backlog; other core-organisers or volunteers are not expected to do that.
+ - We need to adapt our culture of note-taking an documentation to this new model to ensure that all core-organisers can contribute to the effort and benefit from it.
* November 20, 2021