On 02/24/2015 06:53 AM, Dan Smith wrote: ...
- Using a hosted gerrit service (or running it myself)
- Pushing proposals up somewhere, with patches to the mailing list for review, but with a pull request url for actual merging
Any comments on those?
+1 for switching to git and using gerrit. You appear to be self-hosting plenty as it is, what's one more service? :)
I too am not a huge fan of github. It's nice, but it constantly confounds me when I'm trying to do simple things. So -1 on that.
It's also worth noting that nothing prevents us from providing both git and mercurial repositories. Just as I am using hg-git to create a private git repository, so too can it be used to create a mercurial repository from a git repository. Current users can pull from it and continue to use their existing hg-centric workflow.
Just as we could write a script to convert git patch series to mercurial format, the same can be done in reverse. Switching to git will require retooling, so simply consider that as part of the cost. Thus, current mercurial die hards would not be left in the cold; their process should be left virtually unchanged. Mostly. This proposal was all rather off-the-cuff, so there may be use cases that I overlooked.
Cheers,