<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Mar 18, 2017 at 7:27 AM, Pranith Kumar Karampuri <span dir="ltr"><<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@redhat.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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Mar 16, 2017 at 7:42 AM, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi All,<br>
<br>
We have been working on a proposal [1] to make the lifecycle management of Gluster maintainers more structured. We intend to make the proposal effective around 3.11 (May 2016).<br>
<br>
Please review the proposal and let us know your feedback. If you need clarity on any existing aspect or feel the need for something additional in the proposal, please feel free to let us know.<br></blockquote></span><div><br><span class=""><ul><li class="m_-8377674958619570935gmail-">
<p>It’s okay to drop a component if they are not able to find
time/energy. Owners are requested to minimize disruption to the project
by helping with transitions and announcing their intentions.</p>
</li></ul></span>How and to who should it be communicated that a owner/peer is doing a bad job and there are better alternatives for the component?<br><br></div></div></div></div></blockquote><div><br></div><div>All feedback should be directed to the project and community leaders. At this point in time, please direct any feedback (both positive and negative) to Amye, Jeff and me.</div><div><br></div><div>Thanks,<br></div><div>Vijay </div></div></div></div>