# Feature OP-16455 - Sun-setting of Repository module

Project: OpenProject
Status: in specification
URL: https://community.openproject.org/work_packages/OP-16455

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Wieland Lindenthal |
| Accountable | Wieland Lindenthal |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**Explanation/Motivation**

First of all, with this work package I intend to start a discussion for sun-setting/removing the "Repository" module. It is a module that we have been maintaining for quite some years, already, without giving it any updates. It still stems from early Redmine days. In the meantime better systems for collaboration on program code have evolved, like GitHub and GitLab. Both allow the hosting of code and offer better workflows such as pull/merge requests, code reviews etc. To both OpenProject has useful integrations that are used on production systems for quite a while. 

Now, when innovating on OpenProject the Repository module often "stands in the way". For example it adds notes to a work package **Activity**, while they are actually not real comments. When updating and improving the **Activity** tab those commit messages caused quite some maintenance work that we do not see worth it anymore. We could have spent that time on improving features that benefits far more people.

I therefore propose to sunset the Repository module. And in case of objections, I am listening for good reasons why we should not do it. Please leave your comments here.

**Feature description**

**As** an administrator of an OpenProject instance having the "Repository" module enabled, e.g. by connecting a local Subversion oder Git repository  
**I want to** be informed in advance that the "Repository" module will be removed in the following major release  
**so that** that I can plan and execute a migration to an alternative like GitLab and integrate it via OpenProject's GitLab integration. Or chose the GitHub integration.
