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 threadAleksandra Fedorova Mar 29, 2021

@clacke One of takeaways I got from the Social Architecture (https://hintjens.gitbooks.io/social-architecture/content/) was that community changes over time. And priorities can be different depending on the size and maturity of your project. Do you think you can add the concept of *age* here as well?

For example if I am just starting a new project, implementing the whole framework would be an overkill. What should I do first? Or do you think it is the same for all?

Introduction Β· Social Architecture

Show threadclacke: exhausted pixie dream boy πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›Mar 29, 2021
@bookwar I think that a small project should place code quality higher, but otherwise I think the order here represents the order of implementation.

Maybe that means the growing project is the right mental model to order these. Maybe that means my ordering is wrong, as I felt the need to make an exception.

And I think there is no shame in a young and small project not implementing all the levels. If you don't yet have a community, how could you mistreat it?
Aleksandra Fedorova :fedora: (@[email protected])

14 Toots, 30 Following, 12 Followers · CI/Devops/Infra Engineer; Fedora CI SIG, Fedora Council member; PhD in Geometry and Topology; she/her

Show threadAleksandra Fedorova Mar 29, 2021

@clacke I was thinking that If I am just starting, I don't yet have the community to govern. So I shouldn't build a complex process for it. But I do already have the code to write and things like docs might be important.

On the other hand if you don't start with the right idea about governance you might never get the community.

Maybe rather than picking items from the list you need to take it all. But for every item make just a small step in it. And then grow slowly but in all directions.

Show threadclacke: exhausted pixie dream boy πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›
@bookwar Hmmm, yes, you are right. I didn't quite realize that.

They are pretty vague, so each of them do allow a range from simplest process that makes a token attempt to full-blown legal-grade regulatory framework.

It's probably good to sow the seeds as early as possible, yes. It's not how I imagined it, but your idea is better.
Aleksandra Fedorova :fedora: (@[email protected])

14 Toots, 30 Following, 12 Followers · CI/Devops/Infra Engineer; Fedora CI SIG, Fedora Council member; PhD in Geometry and Topology; she/her

Mar 29, 2021 at 9:29pmWeb
Show threadAleksandra Fedorova Mar 30, 2021

@clacke I like the "seeds" term.

Also the framework is really helpful for that. Imagine, I am starting, and I have so many things to do, starting from the code to write.

And I can point to the framework and say: I am going to work in that direction with my project. Not following every bit and every rule, but setting the direction.

And by using this declaration I buy myself time to figure out the exact steps I am going to take. I also tell people that they can help me with it.

Show threadAleksandra Fedorova Mar 30, 2021

@clacke

I think this is the implicit expectation which I have whenever I see project with any of the FOSS-compatible licenses. I assume that it is not just the license, which author wants out of this.

And then all those weird misunderstandings happen. Because license alone doesn't really imply any of those other things you have in your list.

GPL doesn't really say the the code needs to be readable. Or that you need to share instructions how it can be built.

Show threadclacke: exhausted pixie dream boy πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›Mar 30, 2021
@bookwar I thought the Corresponding Source included human-executable build instructions, but you are correct. It explicitly says source code.
Aleksandra Fedorova :fedora: (@[email protected])

14 Toots, 30 Following, 12 Followers · CI/Devops/Infra Engineer; Fedora CI SIG, Fedora Council member; PhD in Geometry and Topology; she/her