Research maintains a lot of code on GitHub (they have their own GitHub team).
Hosting all our code in one place is desirable:
- Makes code searching easier
- Gives us a full picture of our code
- Canonical entry-point into our software
Ideally we'd be able to support the needs of Wikimedia-related code with our in-house hosted infrastructure. Moving projects from GitHub into GitLab was one of the reasons we decided to explore GitLab in the first place.
Research finds value in GitHub's Issues, and would like to use them in GitLab. Issues and wikis are turned off for repos on our GitLab instance. I've left issues on for the repos/research subgroup so they can experiment with Issues.
Just as hosting all our code in one place is desirable, keeping all our tasks in one place is desirable. As part of this experiment I've asked Research to keep track of how they’re using issues to answer the following questions:
- Is GitLab's issue feature comparable to GitHub's issue feature? Is there anything preventing you from fully migrating from GitHub to GitLab?
- What does GitLab issues provide that is not provided in our Phabricator?
- What types of tasks are tracked via Research vs what is tracked in GitLab?
- What effect does GitLab hosting have on collaboration outside your team?