Fork Reva

[kobergj]

Description

We are currently using a sub branch in the cs3org for reva. This is suboptimal. We do not have control over the source as the cs3org could delete our branch at any time. We need to fork reva to the owncloud org to have full control over the code.

User Stories

• As a developer, I want to have control over code I wrote myself so that I can quickly improve and maintain it.

Value

This will help maintaining and improving ocis drastically

Acceptance Criteria

• A fork of the cs3org/reva exists in the owncloud organization (@DeepDiver1975 has permissions to create it)
• Update the current owncloud/reva fork to newest version of cs3org/reva edge branch
• The default branch is called main and is protected
• The owncloud fork must NOT import anything from cs3org/reva (imports/scripts need to be adjusted)
• There are no mentions/imports of cs3org/reva anywhere in owncloud/reva.
• Ocis imports the owncloud fork instead of the cs3org original everywhere
• There are no mentions/imports of cs3org/reva anywhere in owncloud/ocis.

Definition of ready

• Everybody needs to understand the value written in the user story
• Acceptance criteria have to be defined
• All dependencies of the user story need to be identified
• Feature should be seen from an end user perspective
• Story has to be estimated
• Story points need to be less than 20

Definition of done

• Functional requirements
  • Functionality described in the user story works
  • Acceptance criteria are fulfilled
• Quality
  • Code review happened
  • CI is green (that includes new and existing automated tests)
  • Critical code received unit tests by the developer
• Non-functional requirements
  • No sonar cloud issues
• Configuration changes
  • The next branch of the ocis charts is compatible

[DeepDiver1975]

fork already exists: https://github.com/owncloud/reva - but 4yo

[phil-davis]

Also need to consider what CI to run and set that up.
I suppose, at least at first, run the drone pipelines in the existing .drone.star and they will run on the ownCloud drone CI systems (not on the cs3org drone server).
Will need to check references to branch names in .drone.star and other related files.

[DeepDiver1975]

Also need to consider what CI to run and set that up.
I suppose, at least at first, run the drone pipelines in the existing .drone.star and they will run on the ownCloud drone CI systems (not on the cs3org drone server).
Will need to check references to branch names in .drone.star and other related files.

FYI: drone is active on the fork