[Bug 577150] Eclipse Foundation service cleanup superbug
| Bugzilla Link | 577150 |
| Status | NEW |
| Importance | P3 normal |
| Reported | Nov 09, 2021 11:01 EDT |
| Modified | Dec 01, 2021 09:54 EDT |
| Depends on | 451571, 577151, 577152, 577153 |
Description
The webmaster team would like to try and reduce the number of services that projects may need to interact with, and we are specifically looking to shutdown the following services:
Bugzilla
Gerrit
MediaWiki
I'll open dependant bugs for each of these services so that we can collect community feedback.
This is likely to be pretty contentious, but I feel it's worth noting that we're looking a year or so into the future here.
Activity
added Bugzilla Cross-Project legacy labels
The other service for this list is the forums? (Bug 451571)
By Tim Ward
The Eclipse sensiNact project currently uses Gerrit for incoming contributions. Would it be possible to work through GitHub and use Pull Requests instead? I have seen at least a few other Eclipse projects using GitHub. I assume that there's some sort of mirroring managed by the Eclipse team?
(In reply to Jonah Graham from comment #1)
The other service for this list is the forums? (Bug 451571)
Great point Jonah, I'll add that bug as a blocker to this one.
(In reply to Tim Ward from comment #2)
Would it be possible to work through GitHub and use Pull
Requests instead?Yes, we can certainly help you move your project to either Gitlab or Github.
We don't do any mirroring, it's a complete 'lift-and-shift' as they say. Now there are a couple of caveats: namely that this is just a move of the code repos. Bugs are not transferred(merely archived here, so either close them or pick a desired 'state' for them), and you should clean up any outstanding Gerrit reviews prior to the move.
We've been expecting projects to move organically to either Github or Gitlab over time, but that has been a pretty slow process.
-M.
By Tim Ward
(In reply to Eclipse Webmaster from comment #3)
(In reply to Tim Ward from comment #2)\
Would it be possible to work through GitHub and use Pull
Requests instead?
Yes, we can certainly help you move your project to either Gitlab or Github.Our preference would be GitHub
We don't do any mirroring, it's a complete 'lift-and-shift' as they say.
Now there are a couple of caveats: namely that this is just a move of the
code repos. Bugs are not transferred(merely archived here, so either close
them or pick a desired 'state' for them), and you should clean up any
outstanding Gerrit reviews prior to the move.A 'lift-and-shift' is no problem for us as it keeps the commit history. I've cleaned up Gerrit and there's nothing left there that's of interest. The only two open Bugzilla bugs were very old. I've marked them as "won't fix" and they can be added as GitHub issues by us after the move.
Is there anything else that you need from us before the move can start?
By Dan Heidinga
From an OpenJ9 perspective, our primary use of bugzilla is for security defects as bugzilla allows "private" bugs with limited access. This is needed to ensure the issue isn't disclosed before the fix is ready.
What would replace the private bugzilla bugs?
I'm not aware of similar github capabilities (and not familiar enough with gitlab to know about it).
I can confirm that we (Eclipse Lyo, a Technology project) used all of the tools listed in this ticket and then migrated to the alternatives (Bugzilla -> GH issues, Gerrit -> pull requests, Mediawiki -> Github Pages hosted static site built with Markdown and used Pandoc to convert wiki to markdown). One thing I don't see covered is migration from the forums. We have migrated to a self-hosted instance of Discourse, but we only did that because our sister project (OASIS OSLC Open Project) self-hosts and we simply got our own forum category there. I am not sure Github is a proper alternative to a forum. For us, forum also nearly replaced the mailing list as well except for the release-related activity (which in my opinion is a good reason for ensuring Eclipse is in control of whatever replaces forum) mainly because of the mailing list signup barrier for the newcomers (our Discourse instance allows sign-in with a Github account).
(In reply to Tim Ward from comment #4)
Is there anything else that you need from us before the move can start?
Just to keep this bug a little more focused I've filled 577266 for the sensiNact move, so lets discuss things over there.
(In reply to Dan Heidinga from comment #5)
I'm not aware of similar github capabilities (and not familiar enough with
gitlab to know about it).Gitlab does have a concept of confidential issues(
https://docs.gitlab.com/ee/user/project/issues/confidential_issues.html) which should do the trick.-M.
Gitlab does have a concept of confidential issues(
https://docs.gitlab.com/ee/user/project/issues/confidential_issues.html)\ which should do the trick.This is something that probably requires a little more thought. For a project that's hosting repositories on GitLab this is all a no-brainer: confidential issues will just work.
I've updated the handbook to use the "EMO" GitLab repository [1] for requesting a CVE. The issue used for that could also be used to discuss mitigation. It's not entirely clear to me whether or not we have the means of adding arbitrary committers in copy to participate in discussions. AFAIK we can't just @-reference random committers without first adding them to one team or another.
(In reply to Andrii Berezovskyi from comment #6)
One thing I don't see covered is migration from the forums. We
have migrated to a self-hosted instance of Discourse, but we only did that
because our sister project (OASIS OSLC Open Project) self-hosts and we
simply got our own forum category there. I am not sure Github is a proper
alternative to a forum.Your mileage may vary on this of course but we (Eclipse RDF4J) have fairly recently switched to using Github Discussions and Gitter as discussion / Q&A services, and we are finding it much to our liking.
My experience with GH issues that they are a great mess. The search interface is quite unusable compared to bugzilla. Are there experiences to use alternative search interfaces? Or build one?
Also, I like the potential duplicate detection when submitting new bugs. I would expect to have such a function also with the new approach.
In general I think using GH/GL would improve acceptance by contributors.By Christoph Laeubrich
(In reply to Karsten Thoms from comment #11)
My experience with GH issues that they are a great mess. The search
interface is quite unusable compared to bugzilla.Can you explain more? I find it quite useful while at bugzilla I hardly find anything (most probably I'm to dumb to use it ...), of course it depends how specific you name the bug, and assign useful labels, beside that GH provides a quite powerful search language:
https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests
I'm not sure if that was mentioned here somewhere or on linked bugs, but this live document collects current proposal state for Eclipse platform:
https://docs.google.com/document/d/1dFAGX2P5cKnmfppyGhTqUIt0iGAHaRXm1BW7_hVufBw/
Feel free to contribute.
marked this issue as related to #187
marked this issue as related to #679
marked this issue as related to #680
marked this issue as related to #681 (closed)
We are requesting your input on this proposed deprecation/migration plan for Gerrit and Bugzilla:
mentioned in issue #1186 (closed)
