commit 51d2778092a92a6eb5f8cc51f113176f2c3059f5
parent e41f7806e0697aab56b296ea4f6a23080113d4a9
Author: ugrnm <ugrnm@web>
Date: Tue, 8 Apr 2025 09:03:21 +0200
ongoing rewrite of the three levels
Diffstat:
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/three_levels.mdwn b/three_levels.mdwn
@@ -1,28 +1,31 @@
-goal of this doc: find a good narrative and structure for discussing
+goal of this doc: find a good structure for discussing
pmc, across fields, at any level, and in a way that is representative of
the whole pmc spectrum from its daily practical considerations to its
most speculative ambition.
This could be used to better explain the scope of pmc and also help
-structure the wiki landing page to help new readers directing themselves
-and could help create the main sections of the forum.
+structure discussions about pmc, to make it clear that there is.
1. collective problematisation
==============================
-purpose: onboarding
+purpose: framing, scoping, online/offline spaces to discuss and organise
-framing the urgency, newbie corner, staying up to date, relevant events,
+framing the urgency, staying up to date, relevant events,
+creating a spaces to problematise together ICT, the data centre industrial
+complex, encouraging people to share their POV and experience, raising
+awareness that you do not need to be a software engineer to have opinions, ideas,
+and lead critical research on the sad state of ICT
Focus on: the bigger picture, helping ppl figure what pmc can be in
their context/situation, initiatives that can be inspiring for
organisations, schools, collectives, etc. ICT is everywhere, so it
-should not be hard to find a relevant point of friction.
+should not be hard to find a relevant point of friction.
-2. practical degrowth now
-=========================
+2. computational degrowth now
+=============================
purpose: working with what is avail now
