What if we stop treating managed cloud services as products or services and start talking about them as projects or communities.

There is a Debian project, you can not copy it but you can use it or you can join and participate.

Same for the whatever service you have. For example email-as-a-service. Git hosting as a service. Database as a service.

You may have services ruled by benevolent or not so benevolent dictators, but you can also have services with open governance and ways to contribute

@bookwar Yes I think the broad principles of "cooperative technology" would help with this. It's not just about the copyright of the code.

@be I am thinking now if one server in fediverse can be taken as a model example for the cooperative technology service. And how we can describe the criteria for it.

It is a service, it has code and infrastructure, and needs documentation. It also has users which should participate in the governance.

@be @bookwar honestly, I don’t really understand the vision here.

@kev I don't think there is a finalized vision

We are playing with ideas described in cooperativetechnology.codeberg


Something involving users and contributors in infra/docs/administration and governance.

But I am not ready to suggest practical steps yet

@be we may want to try it via some separate prototype first :)

@kev @bookwar Yeah, we don't really have a specific vision yet. We're discussing what that could be.

@bookwar @be that's interesting! I've been wondering what the overlap between copyright and cooperative software would be. On most of my projects I create a list of contributors for copyright purposes and put "The contributors" in the by line. Maybe instead if it were managed cooperatively the collective or co-op would get the copyright, and then anyone could become a member of that (so it doesn't matter which project the co-op maintains, you all share collective ownership of all of them).

@sam @bookwar I don't think it really matters either way as long as the complete list of copyright holders is clearly documented.

@be @bookwar If it's contributors though it sort of makes it just coders. If it's co-op owners (and you subscribe to the cooperative principal of voluntary and open membership) anyone can become an owner without having to know how to code (even if there's no current technical documentation or design work to do or what not). Also if its a foundation like Apache and you work on one project, you now have collective ownership over *all* the projects, not just that one.

@be @bookwar and of course if you apply this to services like the OP said, it sort of takes on a consumer co-op model where the users of the service also have some control (which is good I think as long as it's also balanced against the workers stake so the workers don't get screwed over by it).

Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.