engineering. So what's the reason behind that?
On 3 February 2015 at 22:51, Stormy Peters <
sto...@mozilla.com> wrote:
> I would expect the writing team and the engineering team to still have
> their own discussion lists for everyday work.
>
> Stormy
>
> On Tue, Feb 3, 2015 at 2:38 PM, Eric Shepherd (Sheppy) <
>
eshe...@mozilla.com> wrote:
>
> > As I recall, the purpose behind mdn-drivers was to provide a low-traffic
> > list on which people with a vested interest in ensuring that MDN was
> > functioning to meet their needs could share concerns; this was meant to
> > include people from other teams, including engineering, management, and
> so
> > forth. I know we used it that way from our end, but I guess I don't
> > actually know how well it took hold among other teams.
> >
> > At any rate, these changes generally make sense to me (and don't seem
> like
> > very big changes, so yay!).
> >
> > My one question is this: Is writing/content discussion meant to move from
> > dev-mdc to the new mdn list? The idea was to keep writing discussions
> > separate from engineering discussions in order to avoid anyone having to
> > wade through conversations they had no interest in. Certainly the dev
> team
> > doesn't wan to be involved in our debates on changes to the grammatical
> > style guide or that kind of thing. :)
> >
> >
> > On Tue, Feb 3, 2015 at 3:00 PM, Stormy Peters <
sto...@mozilla.com>
> wrote:
> >
> >> With some of the recent changes in teams, we are proposing to change up
> >> the
> >> mailing lists so that they more closely align with working teams and
> >> initiatives.
> >>
> >> *ACTION: Please sign up for the new MDN list if you wish to continue to
> be
> >> part of MDN discussions:
https://lists.mozilla.org/listinfo/mdn
> >> <
https://lists.mozilla.org/listinfo/mdn>.*
> >>
> >> *Mailing lists:*