aboutsummaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
authorKatharina Fey <kookie@spacekookie.de>2020-04-08 18:44:00 +0200
committerKatharina Fey <kookie@spacekookie.de>2020-04-08 18:46:39 +0200
commit5da97965aac7f8bb84beba083b8afc2ae9397bf8 (patch)
tree5e70a92a2a4f1b329d7f7b64ef2b4a5bb9c13b44 /content
parentf34e5b2cbe7f496b5492efcee659af8b2a1832b3 (diff)
Publish "how to run a community" post and header fixes for FF
Diffstat (limited to 'content')
-rw-r--r--content/blog/116_how_to_run_your_community.md21
1 files changed, 13 insertions, 8 deletions
diff --git a/content/blog/116_how_to_run_your_community.md b/content/blog/116_how_to_run_your_community.md
index 32130e6..2e1372d 100644
--- a/content/blog/116_how_to_run_your_community.md
+++ b/content/blog/116_how_to_run_your_community.md
@@ -1,15 +1,15 @@
Title: Rust, or: how to run a community
Category: Blog
-Date: 2020-04-09
+Date: 2020-04-08
Tags: free software, culture, politics
-Status: Draft
+
This will very much be an off the cuff post about community building
with insights that I've seen from various communities I was a part of
in the last 10 years. None of this is to be taken as facts, and is
entirely personal opinion. I do hope however that this post might
make one or the other think about how we run communities.
-Really...I'm just bored and want to write something.
+Really… I'm just bored and want to write something.
The communities I've been a part of involve Rust, Fedora, Moonscript
(a lua coffee script type), libgdx (a Java game framework), Nix(OS),
@@ -39,12 +39,17 @@ but very much embracing the fact that projects are run by many
individuals that chose to collaborate on something larger than
themselves.
-The reason why I'm such a big fan of e-mail collaboration via mailing
-lists (both for conversations and sending patches) is that it
-encourages this separation. And there's large projects that have
-grown into little bubbles that still work on a shared "product",
-without having to all do it in the same place: the Linux kernel.
+The reason why I'm such a big fan of [e-mail collaboration] via
+mailing lists (both for conversations and sending patches) is that it
+encourages this separation. A project that forces people who
+cross-collaborate to jump from tool to tool is just as centralised as
+a project that only has a single communication channel. But there's
+definitely examples of projects that have grown into little bubbles
+that still work on a shared "product", without having to all do it in
+the same place: the Linux kernel.
Whether you agree or disagree with my take on e-mails, I think we
should all be aware of the finite size that a community can have. And
at what point should we start to embrace community mitosis?
+
+[e-mail collaboration]: https://spacekookie.de/blog/collaborating-with-git-send-email/