-
Notifications
You must be signed in to change notification settings - Fork 52
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
people/communication.md: add a chapter on communication
- Loading branch information
Showing
3 changed files
with
26 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |