Re: https://phpc.social/@grmpyprogrammer/110533726289831992

This is why I am all in on #CoopSource.

#Convene is an operating system to power user-and-moderator owned #cooperatives; with our current "built in" apps providing regional #eCommerce / #Delivery and #Blogging.

#RubyFriends *could* build a #Forum or a #LinkAggregator using #ActivityPub / #Fediverse standards in #Convene, which means any #Coop can host hundreds of small domains with low scaling costs

This emphasis on healthy boundaries and healthy relationships between people is what differentiates #CoopSource.

With #CoopSource, we strive to build in a way that can be replicated by those who align directly with our points or unity, and scale not vertically by accumulating more for fewer and fewer but horizontally, redistributing the wealth created by the digital economy broadly; leveraging our privilege to create wealth for those white supremacist imperial patriarchal capitalism exploited.

But that means #ZincCoop is in a kind of weird spot. I don't want to charge the lovely folks at #NOBAWC or #USFWC to subsidize my time; since I don't have more availability anyway; but I would *love* for networks such as these to have their internal IT Directors acting a liaison for the national/multi-national collection of #CoOpSource co-conspirators, contributors, and maintainers

@Zee does #CoopSource have its own web presence, info, membership/adopters, etc etc?

(I like the idea...)

#CoopSource is when software-enabled cooperatives apply their limited design and engineering budget towards their most immediate high-value problems and there are low-friction affordances for other cooperatives to leverage the output of that labor.

#CoopSource is an informal network of cross-compatible software for community and worker owned enterprises.

Most often the software is compatible at the "Deploy it In the Same Datacenter" level, sharing hardware but in process, container, or even virtualization layer isolation.

These pieces will talk to each other using federated protocols, because sandbox and process-level isolation is necessary for security in low-trust environments.

The most important part of any digital cooperative is neither "moving fast" nor "breaking things" but rather to build trust and sustain things.

For well-capitalized digital cooperatives, they may be able to hire customer development and product development teams to create new solutions.

Most cooperatives, however, will rely on "off-the-shelf" infrastructure and software vendors.

The intersection of "Proprietary"-eseque and open-source-esque #CoopSource is going to be fascinating.

@g So, a Coop can operate as an LLC or a Corporation; the important parts (from a licensing perspective) are:

1. Does the legal entity formally adopt the #Rochdale principles in its ownership and working agreements?
2. Is it a member of a regional cooperative network?

If both of those are true, then #Convene as #CoopSource offers an MIT-tier license.

@boris @andric
I know.

#CoopSource 🙃

Now to the why! How are benefits created by teach?

A. You assemble the appropriate #OSS tools to create the benefits...

_or_

B. You pay someone to design and build something for you.

_or_

C. You buy or rent existing tech from capitalist entities.

#ZincCoop changes all that by providing fully-packaged #CoopSource software for rent or purchase in a #ClientCooperative that distributes the wealth we capture to Maintainers and Contributors rather than Investors.

@strypey This is why I #ZincCoop uses a highly permissive proprietary license that we grant no-questions-asked to organizations that are structured as worker #cooperatives; as verified via a regional #Cooperative network.

The Cooperative commons (or #CoopSource) is distinct from #OpenSource and #FreeSoftware, and I don't really ascribe to either OSS/FS principles due to their lack of grappling with power dynamics.