Could current existing code please be added to git.coop/meet?

Technology Operations
#1

I note that on https://www.org.meet.coop/getinvolved.html

It states:

Code - We host all our code at the cooperative GitLab instance at git.coop/meet.

But at present I don’t think that is actually true.

(git.coop/meet is also linked to from Code in the main menu top right too, of course).

Please could those repos be updated to include our code current running code? (which I think is the now maybe the same a Collocall code @hng?). I think at present that repo still just the stuff @decentral1se and @chris worked on?

Thanks!

Landing page customisation and translation support
Join LibreHosters network
#2

Good point. AFAIK, there is still a running discussion on opening up sources used internally at Collocall with regard to competition and licensing. All super valid points from what I understand. This doesn’t mean things will not go the way of getting all sources in the open at some point but there are still some things to decide on. I’m a bit out of the loop these days but hopefully this is not completey wrong :wink:

1 Like
#3

Ok thanks for the update Luke would like to get more clarity on this in due course.

For me part of the whole point of meet.coop is to create commons and for me part of that is insuring that our code is itself an open commons.

2 Likes
#4

Although BigBlueButton itself is under the LGPL, Scalelite is under the AGPL, of course I am not a lawyer, but even if this doesn’t require that code that is used to provision Scalelite servers isn’t also released under the AGPL it does beg the question, can The Online Meeting Cooperative call itself an “Open source cooperative video conferencing platform” when none of the code written and used by the project to provision the video conferencing servers is available to the users of the service?

The Ansible code used to provision the WordPress, Nextcloud, Kimai, MediaWiki sites, the Matomo instance used and this Discourse server is released under the GPL and is available at git.coop.

2 Likes
#5

Yes, I think the issue to publish the current code as it is being deployed by Collocall to run our Greenlight & BBB servers is already on the tech.circle agenda for months. It should be top priority by now :slight_smile:

Maybe @hng and @dvdjaco know more about it?

agree that this is not so much a legal issue - we’re not using Scalite yet, and the LGPL license doesn’t require to publish the code one runs which does do the AGPL - but it is a commitment to the community in terms of transparency and reproducibility in general.

2 Likes
#6

Yes, I agree that we should be publishing all the code we use for our deployments. @hng recently made some progress on this but I understand they’ve been extra busy with the new lockdowns in Germany. Hopefully we can move forward with this in January.

2 Likes