OCIS mono repository

[exalate-issue-sync]

ocis repo should contain core services contained in ocis binary

ocis-files repo should contain files related code, like fileviewer, webdav API, ocs API, ... find this in other epic.

Open questions

• how to start extensions which are not part of ocis binary
• how can we integrate REVA better, as a library or by adding services in ocis like storage-registry??

[exalate-issue-sync]

Alex Unger commented: we have to figure out how to, during the transition from multiple repositories to a single one, update each subtree and preserve the import paths.

As an example, say during the transition, there is a PR on ocis-settings, we want to update the extension settings on owncloud/mono, but changes to the PR import github.com/owncloud/ocis-pkg/v2, while the current mono repository approach import github.com/owncloud/mono/ocis-pkg. Both modules SHOULD contain the exact same code, diferring only on the import path.

[exalate-issue-sync]

Alex Unger commented: I'm currently addressing the above comment the following way:

1. update the master branch on your local repository.
2. run git subtree pull -P accounts/ ../ocis-accounts master on owncloud/mono project root.
3. resolve merge conflicts (if any) most likely caused by old import paths

[exalate-issue-sync]

Alex Unger commented: git subtree pull -P accounts/ https://github.com/owncloud/ocis-accounts master can be used without needing to locally clone a repository.

[exalate-issue-sync]

Michael Barz commented: Linting and Unit tests work fine using the Makefiles in the subfolders.

Unfortunately I have many linting errors.

WIP in https://github.com/owncloud/mono/pull/1

[exalate-issue-sync]

Michael Barz commented: First CI steps done. Created follow up subtasks.

Parallelization seems to be a good idea.

[exalate-issue-sync]

Remote key is https://jira.owncloud.com/browse/OCIS-462