<div dir="ltr">Following up on this, this revision cycle is meant to be more clear about owners + peers, and less focused on the Red Hat shorthand for levels of responsibility. <div><br></div><div>As far as further goals, I think we can outline Architects and Leads responsibility in a further cycle. I'll let Vijay respond to a further governance document.</div><div> -amye </div><div><br></div><div class="gmail_extra"><div class="gmail_quote">On Fri, Apr 14, 2017 at 3:51 AM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@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="">On Fri, Apr 14, 2017 at 11:40:35AM +0200, Michael Scherer wrote:<br>
> 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>
> 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>
<br>
</span>Indeed, that is one of the things that I mentioned in a similar way on<br>
the previous version of the document. Because the document is aimed at<br>
the Gluster Community, it should address not only the main GlusterFS<br>
project, but also other "components maintained by the community". There<br>
are many different projects in the Gluster Community, of which the<br>
GlusterFS project is one, infrastructure, documentation and probably all<br>
repositories under <a href="https://github.com/gluster" rel="noreferrer" target="_blank">https://github.com/gluster</a> are others. Modules for<br>
Samba, NFS-Ganesha and other "external" projects probably do not count<br>
towards "Gluster proper" and are not included in the "Maintainers 2.0"<br>
approach (mentioning the excluded kinds of projects would be a good<br>
thing too).<br>
<br>
Also, the other relevant "roles" like "Project Lead", "Community Lead"<br>
and "Project Architect" need to be explained with their<br>
responsibilities. A paragraph of their description should probably be<br>
added to the MAINTAINERS [0] file when that gets updated too. A single<br>
naming for the roles would be best (no more "maintainers" anywhere?).<br>
Where would it be listed who has which role in the Gluster Community?<br>
<br>
When I click through the previous conversation, much of the feedback<br>
that was given on an earlier version [1] has not been included or<br>
addressed it seems. In one of the emails Vijay mentioned a "project<br>
governance document" is being written, and that should probably give<br>
more clarity when reading the Maintainers 2.0 proposal. A link to that<br>
document would be helpful.<br>
<br>
Thanks,<br>
Niels<br>
<br>
<br>
0. <a href="https://github.com/gluster/glusterfs/blob/master/MAINTAINERS" rel="noreferrer" target="_blank">https://github.com/gluster/<wbr>glusterfs/blob/master/<wbr>MAINTAINERS</a><br>
1. <a href="http://lists.gluster.org/pipermail/maintainers/2017-March/002368.html" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>pipermail/maintainers/2017-<wbr>March/002368.html</a><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>