commit 9a1fb43c37d31cbcb87ef9c3483a1b3891a08690
parent 9f363876a1bbad20bfe133ea3b53733b723c6860
Author: ugrnm <ugrnm@web>
Date: Thu, 15 Jun 2023 17:55:06 +0200
empty web commit
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/help.mdwn b/help.mdwn
@@ -11,7 +11,7 @@ This is a frequent question, and not an easy one to answer, but here are some su
* Participating: Some permacomputing activities can make sense as individual practices or be related to lifestyle choices and experiments, but this is only one aspect. Another equally important point of leverage is to discuss these things within your institution, union, building, company, town council, to collectively, and also infrastructurally, figure out new ways to discus the impact, regulation or guide the usage and re-use of computers. Join a union, join an environmentalist group, join a citizen science lab, etc. It's also important that users of hardware and software feel confident enough to voice their opinion, specially when the development of these projects is done in a relatively open way. For instance, issue trackers can be important activation sites to voice struggles beyond reporting technical faults.
-* Organizing: Consider starting a local group around permacomputing. You don't have and should not try to work on this topic on your own! Talk to local cultural organisations, hackerspaces, squats, town councils, schools and universities to help organising some events, workshops, skill-sharing sessions, show&tell, etc. Try to bootstrap a small permacomputing community. Make use of our code of conduct to get you started with questions of moderation, make use of the wiki, communicate on the existing lists, chats, or start your own!
+* Organizing: Consider starting a local group around permacomputing. You don't have and should not try to work on this topic on your own! Talk to local cultural organisations, hackerspaces, squats, town councils, schools and universities to help organising some events, workshops, skill-sharing sessions, show&tell, etc. Try to bootstrap a small permacomputing community. Make use of our [[code of conduct|terms]] to get you started with questions of moderation, make use of the wiki, communicate on the existing lists, chats, or start your own!
* Reading/learning: The question of literacy in relation to computational culture is often reduced to staying in the loop with the latest development of the ICT industry and acquiring technological skills. Of course if someone who is not a programmer or frequent user of computers want to dive into permacomputing related practices, some minimal knowledge and jargon could help a lot. But we rarely talk about the other way around. A lot of the radical thinking in computer science, software and hardware engineering, seems to be too often stuck on the same old 60-70s US countercultural ideas. We think that it's important that people with a strong technological background start to catch up with decades of the various strands of computational critique discussed in feminist studies, gender studies, software studies, cultural studies, and also arts and humanities.
