ocis

You don't need to run oCIS in docker, you can use the bare-metal installation: https://owncloud.dev/ocis/deployment/systemd/ just one remark, get the image from assets: https://github.com/owncloud/ocis/releases/tag/v8.0.4

https://opencloud.eu/sites/default/files/media/documents/202... > OpenCloud is based on a fork of the open source software ‘ownCloud Infinite Scale' (OCIS), whose components were co-developed by developers from the science organisation CERN and other active contributors. OpenCloud is now being further developed.. clear focus on data protection, interoperability.. https://owncloud.dev/ocis/ | https://github.com/owncloud/ocis > modern file-sync and share platform.. oCIS breaks down the old [PHP] ownCloud 10 user specific namespace.. makes the individual parts accessible to clients as storage spaces and storage space registries.. WebDAV based oc sync protocol to manage files and folders, ocs to manage shares and TUS to upload files in a resumable way. On the server side REVA is the reference implementation of the CS3 apis which is defined us

According to the README[1] on their source repository, that is, flatly, untrue. They say: > We are very happy that oCIS does not require a Contributor License Agreement (CLA) as it is Apache 2.0 licensed. We hope this will make it easier to contribute code. If you want to get in touch, most of the developers hang out in our rocket chat channel or reach out to the ownCloud central forum. They also say: > Some builds of stable ownCloud Infinite Scale releases provided by ownCloud GmbH are subject to an End User License Agreement. Which seems both reasonable and sensible... [1](https://github.com/owncloud/ocis/tree/master)

The source code is still apache2 licensed, according to the README[1]. That says > Some builds of stable ownCloud Infinite Scale releases provided by ownCloud GmbH are subject to an End User License Agreement. That seems to be exactly the kind of thing that the apache2 license permits. [1](https://github.com/owncloud/ocis/tree/master) It also only seems sensible... if you're offering something like OwnCloud as SaaS, you should probably know enough about it to do your own builds from source.

With this PR https://github.com/owncloud/ocis/pull/6755 I tried to make the policy a bit more clear after we got a nice issue report about it. To be clear: only binary builds of stable versions of Infinite Scale that the ownCloud company is shipping are protected by the EULA. The source code license is Apache2 or AGPL for some parts, and is not touched by this of course. The EULA even allows free use widely, including private, non-commercial and in commercial contexts. It does not allow hosting. We hope to provide a clear and understandable regulation for the project with this, that is protecting our efforts to a certain degree.

https://github.com/owncloud/ocis/pull/6755 - its only for published binary builds.

This seems to only be about binary builds / 'stable releases'? https://github.com/owncloud/ocis#end-user-license-agreement https://github.com/owncloud/ocis/issues/6570 https://github.com/owncloud/ocis/pull/6755/files

Don't expect too much from Nextcloud – it will not be a 1:1 replacement for commercial services from Google, Microsoft, etc. Prepare to spend much time debugging, configuring, reading tickets, etc. If you only want files and Cloud office, consider using alternatives like Seafile[1] or the new OwnCloud rewrite in Go called OCIS[2], which are MUCH more stable than Nextcloud. [1]: https://www.seafile.com/en/home/ [2]: https://github.com/owncloud/ocis

Definitely interesting. Even more impressive on their release notes of Tech Preview: https://github.com/owncloud/ocis/releases/tag/v1.0.0

This reminds me of cozy cloud's rewrite from node.js to go (https://github.com/cozy/cozy-stack ); this seems to be a rewrite from php to go, as well as re-architecturing it: https://github.com/owncloud/ocis Pydio also rewrote itself from php to go with pydio cells: https://github.com/pydio/cells