clacke: exhausted pixie dream boy πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›Mar 29, 2021
I am detecting the skeleton of a user freedom maturity model framework here.

social.finkhaeuser.de/@jens/10…

@jens @be
Jens FinkhΓ€user Β―\_(ツ)_/Β― (@[email protected])

@[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!

social.finkhaeuser.de
Show threadclacke: exhausted pixie dream boy πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›Mar 29, 2021
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
Show threadclacke: exhausted pixie dream boy πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›Mar 29, 2021
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.
Show threadclacke: exhausted pixie dream boy πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›Mar 29, 2021
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.
Show threadBe
@clacke Quality code and documentation are not just "nice". They are a requirement for the freedom to modify the code to be practical.
Mar 29, 2021 at 7:45pmWeb
Show threadclacke: exhausted pixie dream boy πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›Mar 29, 2021
@be Compared to civil behavior, fair governance, usability, accessibility (which I failed to put anywhere in my list), security (which is also missing) and user safety I actually think readable and documented code is a nice-to-have.

It strengthens the ability to achieve half of those things, of course. But we devs can wade through a lot of convoluted and obscure code to get what we want.

Unless actively obfuscated it's an inconvenience and a cost more than anything else.
Be (@[email protected])

7.96K Posts, 141 Following, 444 Followers · I ramble about computers and music here. Some software I work on: https://mixxx.org/ https://tenacityaudio.org/ and various libraries that these use