<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 9, 2015 at 12:06 AM, Martin Jansa <span dir="ltr"><<a href="mailto:martin.jansa@gmail.com" target="_blank">martin.jansa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On Tue, Sep 08, 2015 at 11:39:17AM -0700, Khem Raj wrote:<br>
> On Tue, Sep 8, 2015 at 11:18 AM, Trevor Woerner <<a href="mailto:twoerner@gmail.com">twoerner@gmail.com</a>> wrote:<br>
> > If Richard doesn't want to use gerrit for OE-core, that doesn't exclude<br>
> > others from using it for the layers they manage, does it?<br>
><br>
> yes, however, we should prefer this to run on oe domain, its better<br>
> for project and then if most of layers use it its fine too, it could<br>
> end up<br>
> with same situation as patchwork where oe-core and bitbake do not use<br>
> it actively. other layers do. its not ideal situation but its ok as<br>
> long as<br>
> its makes people productive, we could be open for options its matter<br>
> of volunteers then maintaining the infra for these services.<br>
<br>
</span>I agree, there are not technical reasons for not using it for other<br>
layers, but once we ask contributors to create account on gerrit and<br>
submit all patches through gerrit for *some* layers, then these people<br>
will ask why oe-core and bitbake submissions are different.<br>
<br>
I should also say that I really like gerrit work-flow and review, but if<br>
people continue to send patches to e-mail and someone else will need to<br>
add Change-Ids to them and consolidate them into review-chains, than<br>
it's not as great as it could be if all related people "buy-it" and use<br>
it exclusively.<br>
<br></blockquote><div><br></div><div style="font-size:12.8px"><span class="">Gerrit</span>, despite its good ability to integrate into existing infrastructures might be not the best solution for OE, and I must admit, <span class="">gerrit</span> is not the best tool in the world for reviews, as there are limits in it like missing ability to review properly series of patches.</div><div style="font-size:12.8px"><br></div><div><span style="font-size:12.8px">However, for people who don't like</span><span style="font-size:12.8px"> </span><span class="" style="font-size:12.8px">Gerrit</span><span style="font-size:12.8px">, there is also always a possibility to use GitHub or something similar, like locally hosted GitLab if OE don't want to be dependant on external service.</span></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Regards,<br>
<div class=""><div class="h5"><br>
--<br>
Martin 'JaMa' Jansa jabber: <a href="mailto:Martin.Jansa@gmail.com">Martin.Jansa@gmail.com</a><br>
</div></div><br>--<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">br, Alexander Kanevskiy</div>
</div></div>