<div dir="ltr">I want to clarify my previous reply<br>+1<br>but the new fuel-core would be a small group of the cores who are fully involved in the whole Fuel project.<div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 5, 2016 at 7:22 PM, Alexey Stepanov <span dir="ltr"><<a href="mailto:astepanov@mirantis.com" target="_blank">astepanov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">-1<br>
This is seriously dangerous idea: core-reviewer in fuel-qa does not mean exact skills for +2/W on fuel-octane, for example. Sometimes, because of limited time, reviewer will press +W without understanding patch detail. In repo, which he knows, he can fix issue later by itself, but only of he really knows what he doing.</p>
<br><div class="gmail_quote"><div dir="ltr">пн, 5 сент. 2016 г., 19:14 Maksim Malchuk <<a href="mailto:mmalchuk@mirantis.com" target="_blank">mmalchuk@mirantis.com</a>>:<br></div><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">-1<div>My vision - we should have something like super-core group with a smaller number of the current core guys.</div><div>This is because a lot of current core guys were switched to the other projects and already out of the scope.</div><div>Such guys still can be cores in their former projects and can help sometimes, but only several guys can drive the Fuel.</div><div><br></div><div>P.S. we always can nominate new cores to the specific project individually if you don't like the super-core group idea.</div></div><div class="gmail_extra"></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 5, 2016 at 6:39 PM, Andrew Maksimov <span dir="ltr"><<a href="mailto:amaksimov@mirantis.com" target="_blank">amaksimov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1<div>This is a good proposal, I also think we should have single fuel-core group for all repos. In real life core reviewers won't set +2 or merge to repos with which they are not familiar with. </div><div><br></div><div>Regards,</div><div>Andrey Maximov<br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><span>On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov <span dir="ltr"><<a href="mailto:vkozhukalov@mirantis.com" target="_blank">vkozhukalov@mirantis.com</a>></span> wrote:<br></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Dear colleagues,<br><br></div><div class="gmail_default" style="font-family:monospace,monospace">I'd like to suggest to use common fuel-core group for all Fuel projects instead of having separate independent 'by-project' core groups like 'fuel-astute-core' or 'fuel-agent-core'. <br><br>Pros: <br></div><div class="gmail_default" style="font-family:monospace,monospace">1) It will be easier to access core members (timezone and holiday tolerance)<br></div><div class="gmail_default" style="font-family:monospace,monospace">2) It will be easier to manage single core group (promote new members, remove not active members)<br></div><div class="gmail_default" style="font-family:monospace,monospace"></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Cons:<br></div><div class="gmail_default" style="font-family:monospace,monospace">1) Less of flexibility. Permissions will be the same for all core reviewers in all Fuel projects.<br></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">What do you think?<span><font color="#888888"><br></font></span></div><span><font color="#888888"><div class="gmail_default" style="font-family:monospace,monospace"><br clear="all"></div><div><div><div>Vladimir Kozhukalov</div></div></div>
</font></span></div>
<br></div></div><span>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></span></blockquote></div><br></div>
<br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div><div class="gmail_extra">-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span style="color:rgb(0,0,0)">Best Regards,</span><br style="color:rgb(0,0,0)"><span style="color:rgb(0,0,0)">Maksim Malchuk,</span><br style="color:rgb(0,0,0)">Senior DevOps Engineer<span style="color:rgb(0,0,0)">,</span><br style="color:rgb(0,0,0)"><font color="#000000">MOS: Product Engineering,</font><br style="color:rgb(0,0,0)"><span style="color:rgb(0,0,0)">Mirantis, Inc</span><br><span style="color:rgb(0,0,0)"><a href="mailto:vgordon@mirantis.com" target="_blank"></a></span></div></div></div></div>
</div>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</blockquote></div></div></div>
<br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span style="color:rgb(0,0,0)">Best Regards,</span><br style="color:rgb(0,0,0)"><span style="color:rgb(0,0,0)">Maksim Malchuk,</span><br style="color:rgb(0,0,0)">Senior DevOps Engineer<span style="color:rgb(0,0,0)">,</span><br style="color:rgb(0,0,0)"><font color="#000000">MOS: Product Engineering,</font><br style="color:rgb(0,0,0)"><span style="color:rgb(0,0,0)">Mirantis, Inc</span><br><span style="color:rgb(0,0,0)"><a href="mailto:vgordon@mirantis.com" target="_blank"></a></span></div></div></div></div>
</div>