[Gluster-devel] [Focus Area] Gluster Experience for Developers and Integrations (GEDI)

[Vijay Bellur]

On Mon, Jan 9, 2017 at 3:11 PM, Niels de Vos <ndevos at redhat.com> wrote:

> On Thu, Jan 05, 2017 at 11:22:16PM -0500, Vijay Bellur wrote:
> > On Wed, Dec 14, 2016 at 9:23 AM, Niels de Vos <ndevos at redhat.com> wrote:
> >
> > >
> > >
> > > We would like to make it as easy as possible for other projects to get
> > > in touch with the GEDI team. For that, we propose a mailinglist
> > > (integration at gluster.org) dedicated for engineers that are involved in
> > > Gluster integrations. The main gluster-devel list will most likely
> > > contain too much traffic for developers that do not care about the core
> > > of glusterfs. The new mailinglist may be configured to have its emails
> > > *also* sent to the gluster-devel list so that a wider audience is
> > > reached.
> > >
> > > Please let us know if there are any concerns, questions or other
> > > feedback.
> > >
> > >
> > I like the idea of routing emails from integration on gluster-devel for
> > reaching out to a broader audience. Can we get it done before traffic
> > starts to increase on integration ML?
>
> We can do this, but Nigel expressed that he doesnt want it:
>
>   https://bugzilla.redhat.com/show_bug.cgi?id=1409790#c1
>
>   It's the responsibility of people on the list to CC emails that are
>   potentially interesting to gluster-devel at . Wholesale CCing will only
>   add to the noise on gluster-devel@
>
>
> I do not have a strong preference for one or the other. What do others
> think?
>
>
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.

Thanks,
Vijay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20170109/b82d316e/attachment.html>