From 5da97965aac7f8bb84beba083b8afc2ae9397bf8 Mon Sep 17 00:00:00 2001 From: Katharina Fey Date: Wed, 8 Apr 2020 18:44:00 +0200 Subject: [PATCH] Publish "how to run a community" post and header fixes for FF --- content/blog/116_how_to_run_your_community.md | 21 ++++++++++++------- crumbs/templates/base.html | 2 +- 2 files changed, 14 insertions(+), 9 deletions(-) diff --git a/content/blog/116_how_to_run_your_community.md b/content/blog/116_how_to_run_your_community.md index 32130e6e05d..2e1372d9cc0 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/ diff --git a/crumbs/templates/base.html b/crumbs/templates/base.html index 50ab84ebd8e..1ec37dedc80 100644 --- a/crumbs/templates/base.html +++ b/crumbs/templates/base.html @@ -9,7 +9,7 @@ {# Mastodon verification link #} - + {% block css %}{% endblock %}