<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 9, 2017 at 3:11 PM, 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 Thu, Jan 05, 2017 at 11:22:16PM -0500, Vijay Bellur wrote:<br>
> On Wed, Dec 14, 2016 at 9:23 AM, Niels de Vos <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br>
><br>
> ><br>
> ><br>
> > We would like to make it as easy as possible for other projects to get<br>
> > in touch with the GEDI team. For that, we propose a mailinglist<br>
> > (<a href="mailto:integration@gluster.org">integration@gluster.org</a>) dedicated for engineers that are involved in<br>
> > Gluster integrations. The main gluster-devel list will most likely<br>
> > contain too much traffic for developers that do not care about the core<br>
> > of glusterfs. The new mailinglist may be configured to have its emails<br>
> > *also* sent to the gluster-devel list so that a wider audience is<br>
> > reached.<br>
> ><br>
> > Please let us know if there are any concerns, questions or other<br>
> > feedback.<br>
> ><br>
> ><br>
> I like the idea of routing emails from integration on gluster-devel for<br>
> reaching out to a broader audience. Can we get it done before traffic<br>
> starts to increase on integration ML?<br>
<br>
</span>We can do this, but Nigel expressed that he doesnt want it:<br>
<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1409790#c1" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=1409790#c1</a><br>
<br>
It's the responsibility of people on the list to CC emails that are<br>
potentially interesting to gluster-devel@. Wholesale CCing will only<br>
add to the noise on gluster-devel@<br>
<br>
<br>
I do not have a strong preference for one or the other. What do others<br>
think?<br><span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br></div><div>In my opinion, the core of gluster benefits from being involved in discussions related to gfapi and related interfaces. Hence I have a strong preference to have all emails on integration ML be routed to gluster-devel. Doing it this way will prevent all core gluster developers from signing up for yet another ML.</div><div><br></div><div>Thanks,</div><div>Vijay</div><div><br></div><div><br></div></div></div></div>