Interesting:
Docs is the result of a joint effort lead by the French 🇫🇷🥖(DINUM) and German 🇩🇪🥨 governments (ZenDiS). We are always looking for new public partners (we are currently onboarding the Netherlands 🇳🇱🧀). Feel free to reach out if you are interested in using or contributing to docs.
https://docs.numerique.gouv.fr/login/
#docs #opensource #eu #europe #france #germany #netherlands #collaboration #fosdem
OnlyOffice is certainly more mature as a hosted app. It was born like this, the desktop version was the port. LibreOffice Online is still beta, I think.
So if your interest is in hosting and online editing, OnlyOffice. Also has an interface that’s very similar to MS Office 365, which can be a pro or con to some. LibreOffice has a more traditional toolbar paradigm.
You can try both before string up a server to see what you prefer. They’re both copyleft so no chance of a rug pull.
That’s not accurate. It also takes an absence of a cla (Contributor License Agreement) transfering ownership of patches and a diverse set of major contributors to develop that protection.
GPL protects against outside entities taking over a project via a fork, owners are always free to change the license of what they made.
I didn’t see a cla on either libreoffice online nor onlyoffice, but you would have to contribute some actual changes to see you don’t need to agree to anything and they will accept your contributions without rewriting them later.
In comparison for example audacity makes you transfer rights over code contributions to them. That means they could make audacity closed source at any time and any version from that point would be proprietary. Would they not force contributors to sign that cla, and instead go with a copyleft contribution license, then with going closed source they would violate the licenses under which they use all these contributions.
Basically distributed ownership prevents rug pulls, since ownership beats license restrictions. So you have to check that a project has spread out ownership (independend major contributions) connected by copyleft licenses (standard unless overridden by a (non copyleft) cla)
If such a thing would happen, all you need to do is fork the previous, copyleft, version of the code and go on with life as if nothing happened. That’s an economic disincentive for maintainers to try such shenanigans.
So like OnlyOffice and LibreOffice Online?
Edit: to clarify: both of these products can be self hosted. OnlyOffice’s main business model is to sell hosting services, their software is AGPL v3.
Between OnlyOffice or LibreOffice which do you recommend?
OnlyOffice is certainly more mature as a hosted app. It was born like this, the desktop version was the port. LibreOffice Online is still beta, I think.
So if your interest is in hosting and online editing, OnlyOffice. Also has an interface that’s very similar to MS Office 365, which can be a pro or con to some. LibreOffice has a more traditional toolbar paradigm.
You can try both before string up a server to see what you prefer. They’re both copyleft so no chance of a rug pull.
That’s not accurate. It also takes an absence of a cla (Contributor License Agreement) transfering ownership of patches and a diverse set of major contributors to develop that protection.
GPL protects against outside entities taking over a project via a fork, owners are always free to change the license of what they made.
I didn’t see a cla on either libreoffice online nor onlyoffice, but you would have to contribute some actual changes to see you don’t need to agree to anything and they will accept your contributions without rewriting them later.
In comparison for example audacity makes you transfer rights over code contributions to them. That means they could make audacity closed source at any time and any version from that point would be proprietary. Would they not force contributors to sign that cla, and instead go with a copyleft contribution license, then with going closed source they would violate the licenses under which they use all these contributions.
Basically distributed ownership prevents rug pulls, since ownership beats license restrictions. So you have to check that a project has spread out ownership (independend major contributions) connected by copyleft licenses (standard unless overridden by a (non copyleft) cla)
If such a thing would happen, all you need to do is fork the previous, copyleft, version of the code and go on with life as if nothing happened. That’s an economic disincentive for maintainers to try such shenanigans.