In my last post, I described the current state of Eclipse Gerrit adoption. If you haven't read that post, you might be as surprised as I was to find out how low it is: less than 15% of all Eclipse Projects are using Gerrit, and of those only a few are using it in a meaningful way.
That's understandable, because Gerrit is notoriously difficult to implement. But for those intrepid Eclipse Project Leads who don't mind getting their hands dirty, I'll take the time to detail all of the laborious steps:
- Click Here Now!!
- Replace the summary text "my project" with your project name
- Click "Submit Bug"
- Email a link to the instructions above to the project lead.
- (There isn't a step two.)
- (There aren't any.)
- Dramatic code quality improvement.
- Enforcement of common idioms and project standards.
- Clear workflows and defect traceability for contributions.
- Encouragement of intra-project collaboration and knowledge sharing.
- Greater inter-project transparency.
- Promotion of a more open and equitable Eclipse development process. (Back to that in a second.)
- A bunch of other stuff that, again, I'm too lazy to look up references for. But why am I always the one who has to do all of the work? If you're so damn curious, why don't you just Google "Gerrit Advantages" or something?
An Eclipse Revolution?
Hmmm...let's see if I can put a more positive spin on that....