I am detecting the skeleton of a user freedom maturity model framework here.
social.finkhaeuser.de/@jens/10β¦@jens @be
@[email protected] @[email protected] @[email protected] Oh, absolutely! The only way to do that well is to go for an abstract enough definition!
I harp on about reusability and toolkits and so forth because it's a good example, and whatever definition one comes up with should encourage that.
Maybe reusability is the key term here. Applicability in a diverse range of use cases. Good words elude me for now!
TL;DR by specimen or just brevity; some reordering:
0. FOSS, formal user and developer freedom
1. Inbound = Outbound, contributor parity
2. (4 above) Franklin Street Statement, user data freedom
3. CoC, freedom from discrimination
4 (2). C4, fair paths to governance
5 (4.1). Moderation, user safety
6 (5). Userops, admin practical software freedom
7 (5.1). Community input, user practical software freedom
8 (6). TDD, code quality, malleability, docs, CI/CD, developer practical software freedom
There is the word "community" at level 7 only in the brief version.
That might be me telling myself that you're not true communal software until you're at level 7.
Maybe that's too harsh. Maybe moderation and userops are technical features that would come out of the communal process and community input should be on the level before them.
I am very much convinced that "code and docs are nice" comes last. And I think it is telling that we devs usually place it somewhere around (1) when we choose our projects to contribute to.
@clacke why not replace community input with community ownership? Of course there will always be a case where some protocols need to be agreed upon, but beyond that there should be no excuse for requiring community consensus (via only having one version of a piece of software, controlled by one clique), if your malleable software can't handle this then it's not good enough
@Gnuxie I saw "malleable software" somewhere else earlier tonight. Are people tying a specific meaning to this term? Are you, or do you generally mean that the program should be easy to adapt to new circumstances and requirements?
(basically avoiding the poisoned term "agile")
445 Toots, 45 Following Β· Maximalist Egoist Communist Object Oriented Telephone Characteristics Hackerππβ
Gnu is garbage
πβπ
ΎοΈβπβ NOW!
If I unfollowed you, you post too much and I can't deal with it
I guess I should say I also co-authored this: https://applied-langua.ge/software-and-anarchy.pdf
@clacke well I don't like the term malleable software very much, it is being propagated by the 'malleable systems' collective (https://malleable.systems/), what they really want is dynamic systems but they want to avoid the stigma that for some reason has been associated with dynamic programming languages and allow for a system made from static components that aren't modifiable from within the 'malleable' system to be included in their definition, which I believe is a big problem as it is contradictory and against the goals of a malleable system (as you would want to be able to modify those components).
I wrote a little bit more about this in detail with a good friend here (https://applied-langua.ge/software-and-anarchy.pdf (C-f malleable system)) if you are really interested about this but to be honest with you the ideology we put across in this book i really strong and I don't want to cause any knee jerk reactions because of that. I also don't mind explaining anything if there are more questions
Malleable Systems Collective
The Malleable Systems Collective catalogs and experiments with malleable software and systems that reset the balance of power in computing
@Gnuxie I think even if it's a lego system where you out together closed boxes of inscrutable code, that's still an improvement over the app store where you just get the one closed box that supposedly solves your problem.
Once we're there, I feel like it's a small step to also have open boxes that are made of smaller boxes.
445 Toots, 45 Following Β· Maximalist Egoist Communist Object Oriented Telephone Characteristics Hackerππβ
Gnu is garbage
πβπ
ΎοΈβπβ NOW!
If I unfollowed you, you post too much and I can't deal with it
I guess I should say I also co-authored this: https://applied-langua.ge/software-and-anarchy.pdf
clacke: exhausted pixie dream boy πΈπͺππ°ππ
Gnuxie ππ