<div dir="ltr">Hi Joseph,<div><br></div><div>Thanks for the proposal. Integrating Gerrit (and other ticket systems) into the review process has been discussed several times. However, the mail list has been working well for sheepdog for a long time. And we don't see sticking to maillist for bug reporting and code review is a bad idea at the current stage. </div>
<div><br></div><div><div>But I think the community is still open to Gerrit if it could improve the review process a lot more in the future, e.g. when we have more developers.</div></div><div><br></div>
<div><br></div><div>FYI, Paste some old arguments from our awesome developers on the maillist about Gerrit:</div><div>"</div><div><span style="font-family:arial,sans-serif;font-size:13px">I have some awful experience of </span><span style="font-family:arial,sans-serif;font-size:13px">Gerrit</span><span style="font-family:arial,sans-serif;font-size:13px"> system, it just looks to me</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">lifting higher barrier and throwing more problems than it solves:</span><br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px"> 1 the review process in hidden in the </span><span style="font-family:arial,sans-serif;font-size:13px">Gerrit</span><span style="font-family:arial,sans-serif;font-size:13px"> and not as open as current</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">plain patch in the mailing list</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px"> 2 need more steps of submitting the patch set than current only 'git</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">send-email' one liner.</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px"> 3 the patch set and its history isn't indexable or logged by other</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">system like </span><a href="http://marc.info/" style="font-family:arial,sans-serif;font-size:13px" target="_blank">marc.info</a><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px"> 4 It is very cumbersome than plain mail text.</span><br style="font-family:arial,sans-serif;font-size:13px"></div><div><span style="font-family:arial,sans-serif;font-size:13px">"</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">"</span></div><div><span style="font-family:arial,sans-serif;font-size:13px">IMHO, </span><span class="" style="font-family:arial,sans-serif;font-size:13px">Gerrit</span><span style="font-family:arial,sans-serif;font-size:13px"> is too complex to review patches.</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">When I contributed a patch to OpenStack, I thought that </span><span class="" style="font-family:arial,sans-serif;font-size:13px">Gerrit</span><span style="font-family:arial,sans-serif;font-size:13px"> was a</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">barrier for new developers to join community. However, if I'm in a</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">minority group, I'm not against introducing it.</span><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">"</span></div><div style>...</div><div style><br></div><div style><br></div><div style>Sheepdog is compatible with openstack anyway, even when we have two different review systems, don't we? ;)</div>
<div style><br></div><div style><br></div><div style>Regards,</div><div style>Wenhao</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 17, 2013 at 9:19 AM, Joseph Glanville <span dir="ltr"><<a href="mailto:joseph@cloudscaling.com" target="_blank">joseph@cloudscaling.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">How do people feel about integrating Gerrit at some stage for code review?<br>
<br>
If Sheepdog wants to be closer aligned with OpenStack this would be a<br>
great way of making the 2 ecosystems more compatible. :)<br>
<div class="HOEnZb"><div class="h5"><br>
On Sun, Jun 16, 2013 at 5:13 PM, MORITA Kazutaka<br>
<<a href="mailto:morita.kazutaka@gmail.com">morita.kazutaka@gmail.com</a>> wrote:<br>
> At Fri, 14 Jun 2013 11:44:25 +0800,<br>
> Kai Zhang wrote:<br>
>><br>
>> Hi all<br>
>><br>
>> I'm very happy to announce that a public Jenkins server for sheepdog has been set up.<br>
>> Both server and hostname are sponsored by <a href="http://zelin.io" target="_blank">zelin.io</a><br>
>><br>
>> Please check <a href="http://jenkins.sheepdog-project.org" target="_blank">http://jenkins.sheepdog-project.org</a> for more.<br>
><br>
> Great, thanks a lot!<br>
><br>
>><br>
>> Currently, there are only 2 jobs.<br>
>> One is for daily build. The other is for testing with local driver. (This is a downstream job of former one)<br>
>><br>
>> However, it is still far from enough.<br>
>> The fowling things will be done soon:<br>
>> - add github hook so that each commit will trigger a new build<br>
>> - generate graphical testing report<br>
>> - add jobs for testing zookeeper and corosync<br>
>> - fix testing errors<br>
>><br>
>> For security reason, only login user can configure jobs and sign up has been disabled.<br>
>> It would be very appreciated if you would like to contribute on Jenkins. And I will create an account for you.<br>
><br>
> Can you create an account for me? I'd be happy to help you.<br>
><br>
> Thanks,<br>
><br>
> Kazutaka<br>
</div></div><span class="HOEnZb"><font color="#888888">> --<br>
> sheepdog mailing list<br>
> <a href="mailto:sheepdog@lists.wpkg.org">sheepdog@lists.wpkg.org</a><br>
> <a href="http://lists.wpkg.org/mailman/listinfo/sheepdog" target="_blank">http://lists.wpkg.org/mailman/listinfo/sheepdog</a><br>
--<br>
sheepdog mailing list<br>
<a href="mailto:sheepdog@lists.wpkg.org">sheepdog@lists.wpkg.org</a><br>
<a href="http://lists.wpkg.org/mailman/listinfo/sheepdog" target="_blank">http://lists.wpkg.org/mailman/listinfo/sheepdog</a><br>
</font></span></blockquote></div><br></div>