MDN Services "support"

[Luke Crouch]

mdn-services,

We need to set up some kind of support channel for developers who start
using the first MDN services prototypes. (Security prototype should be
usable by the end of this month.)

We discussed simply setting up sup...@developer.mozilla.org, but we can't
create email aliases at mozilla sub-domains. So, our options are:

1. Direct users to this list for support requests
2. Create a new mdn-servic...@lists.mozilla.org list
3. Direct users to each project's independent channel (e.g., GitHub issue
tracker, bugzilla)
4. Something else I'm not considering?

Does anyone have a strong preference which way we go?

-L

[John Karahalis]

In the early stages, a bug tracker might be best. I suspect most people
will be reporting bugs and requesting features, and even most support
requests will be testaments of unclear or misleading user interfaces.
Capturing the history of requests/confusions someplace permanent, and
someplace that encourages acting upon them, would be super helpful.

> _______________________________________________
> mdn-services mailing list
> mdn-se...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/mdn-services
>



--
John Karahalis
Mozilla
openjck.com

[Stephanie Hobson]

#3 seems like it would have the lowest time drain on our team. Rather than
needing to reply to each email as well as track work it would let us
consolidate/mark as duplicate common requests and manage notification of
bug/request/support fixes from one location.

If we go with bugzilla it would be nice to have a URL with the correct
component etc already selected.

Stephanie.


On Fri, Mar 13, 2015 at 7:29 AM, John Karahalis <jkara...@mozilla.com>
wrote: