<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">+1, I think it is good idea.<div class=""><br class=""><div class="">
Regards,<br class="">Bulat Gaifullin<br class="">Mirantis Inc.<div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 05 Sep 2016, at 20:17, Maksim Malchuk <<a href="mailto:mmalchuk@mirantis.com" class="">mmalchuk@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I want to clarify my previous reply<br class="">+1<br class="">but the new fuel-core would be a small group of the cores who are fully involved in the whole Fuel project.<div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Sep 5, 2016 at 7:22 PM, Alexey Stepanov <span dir="ltr" class=""><<a href="mailto:astepanov@mirantis.com" target="_blank" class="">astepanov@mirantis.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr" class="">-1<br class="">
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 class=""><div class="gmail_quote"><div dir="ltr" class="">пн, 5 сент. 2016 г., 19:14 Maksim Malchuk <<a href="mailto:mmalchuk@mirantis.com" target="_blank" class="">mmalchuk@mirantis.com</a>>:<br class=""></div><div class=""><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">-1<div class="">My vision - we should have something like super-core group with a smaller number of the current core guys.</div><div class="">This is because a lot of current core guys were switched to the other projects and already out of the scope.</div><div class="">Such guys still can be cores in their former projects and can help sometimes, but only several guys can drive the Fuel.</div><div class=""><br class=""></div><div class="">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 class=""><div class="gmail_quote">On Mon, Sep 5, 2016 at 6:39 PM, Andrew Maksimov <span dir="ltr" class=""><<a href="mailto:amaksimov@mirantis.com" target="_blank" class="">amaksimov@mirantis.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">+1<div class="">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 class=""><br class=""></div><div class="">Regards,</div><div class="">Andrey Maximov<br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote"><span class="">On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov <span dir="ltr" class=""><<a href="mailto:vkozhukalov@mirantis.com" target="_blank" class="">vkozhukalov@mirantis.com</a>></span> wrote:<br class=""></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:monospace,monospace">Dear colleagues,<br class=""><br class=""></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 class=""><br class="">Pros: <br class=""></div><div class="gmail_default" style="font-family:monospace,monospace">1) It will be easier to access core members (timezone and holiday tolerance)<br class=""></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 class=""></div><div class="gmail_default" style="font-family:monospace,monospace"></div><div class="gmail_default" style="font-family:monospace,monospace"><br class=""></div><div class="gmail_default" style="font-family:monospace,monospace">Cons:<br class=""></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 class=""></div><div class="gmail_default" style="font-family:monospace,monospace"><br class=""></div><div class="gmail_default" style="font-family:monospace,monospace">What do you think?<span class=""><font color="#888888" class=""><br class=""></font></span></div><span class=""><font color="#888888" class=""><div class="gmail_default" style="font-family:monospace,monospace"><br clear="all" class=""></div><div class=""><div class=""><div class="">Vladimir Kozhukalov</div></div></div>
</font></span></div>
<br class=""></div></div><span class="">______________________________<wbr class="">______________________________<wbr class="">______________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.<wbr class="">openstack.org?subject:<wbr class="">unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/<wbr class="">cgi-bin/mailman/listinfo/<wbr class="">openstack-dev</a><br class="">
<br class=""></span></blockquote></div><br class=""></div>
<br class="">______________________________<wbr class="">______________________________<wbr class="">______________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.<wbr class="">openstack.org?subject:<wbr class="">unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/<wbr class="">cgi-bin/mailman/listinfo/<wbr class="">openstack-dev</a><br class="">
<br class=""></blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div></div><div class="gmail_extra">-- <br class=""><div data-smartmail="gmail_signature" class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><span style="" class="">Best Regards,</span><br style="" class=""><span style="" class="">Maksim Malchuk,</span><br style="" class="">Senior DevOps Engineer<span style="" class="">,</span><br style="" class=""><font class="">MOS: Product Engineering,</font><br style="" class=""><span style="" class="">Mirantis, Inc</span><br class=""><span style="" class=""><a href="mailto:vgordon@mirantis.com" target="_blank" class=""></a></span></div></div></div></div>
</div>
______________________________<wbr class="">______________________________<wbr class="">______________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.<wbr class="">openstack.org?subject:<wbr class="">unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/<wbr class="">cgi-bin/mailman/listinfo/<wbr class="">openstack-dev</a><br class="">
</blockquote></div></div></div>
<br class="">______________________________<wbr class="">______________________________<wbr class="">______________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.<wbr class="">openstack.org?subject:<wbr class="">unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/<wbr class="">cgi-bin/mailman/listinfo/<wbr class="">openstack-dev</a><br class="">
<br class=""></blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><span style="" class="">Best Regards,</span><br style="" class=""><span style="" class="">Maksim Malchuk,</span><br style="" class="">Senior DevOps Engineer<span style="" class="">,</span><br style="" class=""><font class="">MOS: Product Engineering,</font><br style="" class=""><span style="" class="">Mirantis, Inc</span><br class=""><span style="" class=""><a href="mailto:vgordon@mirantis.com" target="_blank" class=""></a></span></div></div></div></div>
</div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>