I generally don't like "viral" license that restrict software use, but I keep thinking about what a "cooperative" software license would look like. Would it restrict use to only members and other software being developed according to the statement on cooperative identity? What about non-profits that aren't operated cooperatively? Would it use some legal definition of "cooperative software" or co-ops as a business vehicle (in places where there is such a thing)?
Maybe it would be deliberately vague. Like it's just a BSD style license except it has an extra clause that says "Commercial use by for-profit entities is forbidden except by members of the cooperative as defined in the bylaws." Then you can specify that contributors are members automatically, other co-ops can become a member for free at the discretion of the co-op, or anyone can buy in. Or maybe it's best to let other cooperative software use it without becoming a member first.
Although I don't know what it means for a contributor to be able to use it commercially. Do they get to use it in any software that's not also cooperatively governed? Only in cooperative software made in their individual capacity? Do contributors to their software who get to exploit that software for commercial gain also by extension get to use the original upstream software? Does this make that clause effectively useless?
And of course:
- license proliferation is bad and licenses do nothing unless you actually enforce them, which most co-ops probably can't do against big commercial entities anyways so this is just a thought experiment.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!