4 ms·
I work on OpenJDK. Here are some steps we've taken to not overly depend on GitHub: 1. Issues stay on a self-hosted JIRA. 2. All PRs get an automatically gener
by pron 6y ago
I work on OpenJDK. Here are some steps we've taken to not overly depend on GitHub:
1. Issues stay on a self-hosted JIRA.
2. All PRs get an automatically generated patch that's posted to the mailing list, and all comments are two-way mirrored between GH and the mailing list.
3. All links to commits in issues don't point directly at GH but at an indirection through our domain.
4. All bots work on both GH and GitLab
This means that we can move off of GH pretty much instantly if the need arises. But self hosting with GitLab just wouldn't serve our goals. We want speed all around the world, and we don't want to spend resources on administration.
- deleted 6y ago[deleted]
- gempir 6y agoTotally agree. Wasting time on infrastructure like self hosting gitlab to be less reliant on Github is not always a good idea. If your project is setup in a way to just git push to another remote and then you're done, then I think it's fine to use Github.
- The_rationalist 6y agoIssues stay on a self-hosted JIRA. It's really sad as you will have order of magnitude less contributions on jira. Couldn't you autosynchronize github.com issues to jira ones? Otherwise, you're hurting the ecosystem as a whole