If you're founding a coop, you're probably more interested in organizational theory than doing the work. There are cost savings when it comes to group buying or trade; so works well for farmers. But to do this for software is not about building better software IMO.
You can kinda see a hint of this in the spelling of Toronto as Tkaronto. I don't think this benefits the list. It's a kind of meta work, a convenient distraction from doing something of value.
If you're a builder you'll preoccupy yourself with the thing you're building. If you're driving by an ideology, you'll spend most of your time there, and legal frameworks will be of secondary concern, a means to an end.
> If you're a builder you'll preoccupy yourself with the thing you're building.
If you're one person building a thing that one person can build, that might be true.
If you're building a thing that needs or merely benefits from having more people doing the building, you almost certainly need to think about how to structure and coordinate what people do. That's true even if your decision is "no structure and no coordination".
Sometimes, that process will be implicit (and likely a more or less direct reflection of the personality of the initial builder). But for the most, once you start involving other people (or they involve themselves), organizational structure and behavior starts to become a thing you have to start paying attention to. Getting it wrong can destroy whatever you're trying to build.
You can kinda see a hint of this in the spelling of Toronto as Tkaronto. I don't think this benefits the list. It's a kind of meta work, a convenient distraction from doing something of value.
If you're a builder you'll preoccupy yourself with the thing you're building. If you're driving by an ideology, you'll spend most of your time there, and legal frameworks will be of secondary concern, a means to an end.