+1.  many times i want to participate the discussion on dev, i have stop on
which maillist i have not booking. the simply way will enhance community's
growing.

2016-03-25 10:49 GMT+08:00 Guangya Liu <[email protected]>:

> +1.
>
> This is actually what OpenStack is doing now. OpenStack has many projects
> and every time we send an email to dev list, we always specify if it is for
> dev or user first, then specify the project as following:
>
> [openstack-dev][Magnum] Integrate Mesos Unified Container to Magnum.
>
> So for mesos, we can do similarly:
> [mesos-dev][allocator] Performance improvement => mesos dev allocator
> working group for performance.
> [mesos-user][container] How can I use appc => mesos user for container
> questions.
>
> Thanks,
>
> Guangya
>
> On Fri, Mar 25, 2016 at 10:40 AM, haosdent <[email protected]> wrote:
>
> > +1 The subject seems use "[MESOS WG][WG_NAME]" xxx would be better
> >
> > On Fri, Mar 25, 2016 at 6:55 AM, Jie Yu <[email protected]> wrote:
> >
> > > Hi,
> > >
> > > This came up during today's community sync.
> > >
> > > Mesos currently has a few working groups for various features:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/MESOS/Apache+Mesos+Working+Groups
> > >
> > > Some of those working groups are using separate mailing lists. That
> > limits
> > > the visibility of some discussions. Also, some people in the community
> > are
> > > not aware of those mailing lists (and the wiki page).
> > >
> > > Therefore, I am proposing that we consolidate all working groups
> mailing
> > > lists to the dev mailing list. To distinguish discussions from
> different
> > > working groups, please use a special subject format. For instance, if
> you
> > > want to send an email to "Mesos GPU" working group, please use the
> > subject:
> > >
> > > "[Mesos GPU WG] YOUR SUBJECT HERE"
> > >
> > > Let me know if you have any comments/thoughts on this!
> > >
> > > - Jie
> > >
> >
> >
> >
> > --
> > Best Regards,
> > Haosdent Huang
> >
>



-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Reply via email to