commit 3401f988917b5e0d902ccdd7ac1e110defe92573
parent 798ab3ffabbb794b5d7f4faa0a41ad0c4cbdfc79
Author: ugrnm <ugrnm@web>
Date: Fri, 2 Jan 2026 13:31:12 +0100
important note on openness
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/expose_the_seams.mdwn b/expose_the_seams.mdwn
@@ -31,7 +31,7 @@ What can YOU do
**When creating and maintaining software, digital tools or infrastructure**
-* Share your projects' source code, blueprints, and design philosophy.
+* Share your projects' source code, blueprints, and design philosophy. Keep in mind that openness alone is not enough, and can even work against the interests of your community. See [[FLOSS]] to learn more about the position of permacomputing in relation to the digital commons.
* Show the inner-workings whenever possible (different technical and non-technical parts of a project).
* Don't automate every aspect of a project to keep knowledge about how things work available to non-experts also.
* Sonify or visualise "background" processes that take computational resources but aren't part of an interaction.
