<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 14, 2017 at 2:40 AM, Michael Scherer <span dir="ltr"><<a href="mailto:mscherer@redhat.com" target="_blank">mscherer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Le jeudi 13 avril 2017 à 18:01 -0700, Amye Scavarda a écrit :<br>
> In light of community conversations, I've put some revisions on the<br>
> Maintainers changes, outlined in the hackmd pad:<br>
> <a href="https://hackmd.io/s/SkwiZd4qe" rel="noreferrer" target="_blank">https://hackmd.io/s/SkwiZd4qe</a><br>
><br>
> Feedback welcomed!<br>
><br>
> Note that the goals of this are to expand out our reach as a project<br>
> (Gluster.org) and make it easy to define who's a maintainer for what<br>
> feature.<br>
> I'll highlight the goals in the document here:<br>
><br>
> * Refine how we declare component owners in Gluster<br>
> * Create a deeper sense of ownership throughout the open source project<br>
> * Welcome more contibutors at a project impacting level<br>
><br>
> We've clarified what the levels of 'owners' and 'peers' are in terms of<br>
> responsibility, and we'll look to implement this in the 3.12 cycle.<br>
> Thanks!<br>
<br>
</span>So, I realize that the concept of component is not defined in the<br>
document. I assume everybody have a shared understanding about what it<br>
is, but maybe not, so wouldn't it make sense to define it more clearly ?<br>
<br>
Is this planned to be done later as part of "We will be working on<br>
carving out new components for things that make logical sense." ?<br>
<br>
As for example, with regard to my previous comment, would<br>
"infrastructure" be a component, would "documentation" be a component ?<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div>My understanding is that there's a working spreadsheet being refined to sort out what's an area that needs a maintainer defined, and what's something that maybe doesn't need a named maintainer. Documentation is a tricky place to get to, because that's something that you do just naturally so that future-you doesn't hate current-you. </div><div><br></div><div>However, I'll see if I can't find that spreadsheet because the above document is more guidelines than practical reality. </div><div>Anything else?</div><div> - amye </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
--<br>
Michael Scherer<br>
Sysadmin, Community Infrastructure and Platform, OSAS<br>
<br>
<br>
</div></div><br>______________________________<wbr>_________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Amye Scavarda | <a href="mailto:amye@redhat.com" target="_blank">amye@redhat.com</a> | Gluster Community Lead</div></div>
</div></div>