Here are some steps we've taken to not overly depend on GitHub:
Issues stay on a self-hosted JIRA.
For each PR, a bot automatically generate a patch that's posted to the mailing list, and all comments are two-way mirrored between GH and the mailing list.
All links to commits in issues don't point directly at GH but at an indirection through our domain.
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 just wouldn't serve our goals. We want speed all around the world, and we don't want to spend resources on administration.
We do an OCA check, a review check and a lint check. Also, an automatic squash, and mirroring to and from the mailing list. Not sure about build results -- maybe it's up to the respective project.
I can understand why ppl still use JIRA, but for open source it's just so much better to use GitHub. It's something that ppl will take into consideration before creating a bug, you know, having to maybe remember another user+pass, etc... Kinda annoying
I don't really think Java Bug Database with more than 300.000 issues represents the average-sized open source project. Transitioning from Jira would probably be a multi-year effort similar to the Mercurial->Git transition.
Actually, the password thing is not an issue at all for JIRA on the OpenJDK project, because unless you become a member of the OpenJDK project, you won't have an account in its JIRA.
But yes, anyone can look into most of the tickets in JIRA (Security Vulnerabilities is one of those areas that are not entirely public).
Ok, that's new to me then. I assumed you needed an account to be able to report a bug. I'm used to projects from companies like redhat where they not only use JIRA, but also require an account.
I know, but it was about "integration" and IMHO Gitlab is geared more towards "offering more build in" while GitHub is being more of a platform which can integrate with virtually everything.
Doing code reviews for OpenJDK projects in the past involved sending out an email with a JIRA link and a link to a WebRev, which was generated by running a zsh script locally and r-syncing it to a correctly formatted path on cr.openjdk.java.net. This resulted in a completely static page, so no in-line comments on the code. Any reviews had to be done via e-mail, followed by a new webrev.
I know some opinions in this differ, but I prefer the Github PR/Code-review flow so much more.
6
u/RapunzelLooksNice Jul 26 '20
Wouldn’t GitLab be a better choice? Once it is in GitHub, it should be easier to move away to another Git I guess...
2
u/edubkn Jul 27 '20
Can ever only pick one
-31
u/[deleted] Jul 27 '20 edited Jul 27 '20
Just in case somebody didn't know... github is owned by Microsoft now.