Moving Bugzilla to git?

Damien damien.nozay at gmail.com
Fri Oct 25 02:08:08 UTC 2013


>
> And about attracting more contributors thanks to a migration to git, I
> absolutely don't believe in this at all. I spent enough time on the
> Bugzilla project to know that it's irrelevant. What matters is the
> language used by Bugzilla, i.e. Perl, and developers coding in this
> language.
>

Speaking for myself only, I would __strongly__ disagree that VCS is irrelevant.

Be it gitorious or github, I like to be able to simply fork something, push,
send a pull request. Some will think it is a "throwing garbage over the wall"
mentality but hey that works for me...

https://github.com/dnozay/bugzilla
https://travis-ci.org/dnozay/bugzilla
Actually I lie, I let Travis test my changes before I throw them over the wall.

Contributing something to bzr goes like this:
https://wiki.mozilla.org/Bugzilla:Developers  <--- 11 steps!
https://wiki.mozilla.org/Bugzilla:Committing_Patches <--- 11 steps!
http://www.mozilla.org/hacking/committer/ <---- errrhhh.

Language matters of course, but I don't want to use bzr. VCS matters too.
I don't want to do anything with bzr; "my religion is against it".
I believe if the tools are easy to use, people will use them.

Contributing to git goes like this:
1. fork the repo.
2. make your changes.
3. push to your copy.
4. you think it's ready, send a pull request


+1 for Gerrit suggestion for review process even though I'm not really a fan.

-
dnozay



More information about the developers mailing list