Skip to content

Commit

Permalink
people/communication.md: add a chapter on communication
Browse files Browse the repository at this point in the history
  • Loading branch information
bagder committed Jan 4, 2025
1 parent 0045c7e commit d979108
Show file tree
Hide file tree
Showing 3 changed files with 26 additions and 1 deletion.
1 change: 1 addition & 0 deletions SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@
* [Contributors are mostly male white westerners](people/male-white.md)
* [Lower the bar to attract more contributions](people/lower-bar.md)
* [Code of Conduct](people/code-of-conduct.md)
* [Communication](people/communication.md)
* [Project](project.md)
* [Just a bunch of people](project/bunch.md)
* [People come and go](project/come-and-go.md)
Expand Down
2 changes: 1 addition & 1 deletion people.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,4 +19,4 @@ are social and complicated creatures.
* [Contributors are mostly male white westerners](people/male-white.md)
* [Lower the bar to attract more contributions](people/lower-bar.md)
* [Code of Conduct](people/code-of-conduct.md)

* [Communication](people/communication.md)
24 changes: 24 additions & 0 deletions people/communication.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# Communication

Successful Open Source requires good and plentiful communication without
friction.

We always prioritize and favour using open solutions and Open Source platforms
and technologies rather than closed ones - even if the proprietary ones often
look shiny and have fancy fatures. Because it is better to practise what we
preach and because it is then less likely that a commercial vendor suddenly at
a whim makes decisions that hurt your Open Source project.

In the before-2000 era using email and mailing lists were the natural choice.
For later generations they are not at all as commonly preferred which actually
is a challenge because going over to web based solution forces you to a higher
degree have to select a *platform* to use for communication.

Whatever technology and platform you use, pick one with low barriers to entry
that makes it easy for newcomers and oldies alike. Closed or open, chances are
that you will use a service that is hosted by others so no matter which you
run with, you will always risk that the service gets shut down abruptly one
day and you get to move on to something else. Just embrace it and accept that
nothing is forever. If data is important to you, make sure you export and/or
back it up regularly so that it survives the death of your current platform of
choice.

0 comments on commit d979108

Please sign in to comment.