Introducing #dev-help on Matrix

[Andrew Halberstadt]

Hello Mozilla developers,

Have you ever had a problem with your workflow or the tools you need to do your job? Have you been bounced around between channels, searching for the right person who knows how to help you out?

Either way, I’m pleased to announce the creation of #dev-help, a new Matrix channel dedicated to helping developers with their issues. This will be the one stop shop for developers to get help with all of their workflow and tooling problems, regardless of where it is in the pipeline. From your editor to the user's screen and everything in between.

The idea is simple, we will do our best to help you directly in this channel without redirecting you to another channel. If we don’t know how to help you, we’ll try to pull domain experts into the channel, so we get comprehensive coverage of the entire development pipeline.

So if you run into any problems with our tooling, workflows, or have any questions, don’t hesitate to drop by and ask!

Cheers,
Andrew

[Andrew Halberstadt]

Quick follow-up, we're having some technical difficulties publishing the room to the room directory. So you'll need to join directly by following the link:
#dev-help:mozilla.org

Or by joining the above room id directly.

Thanks,

Andrew

[Erich Gubler]

Hey Andrew, how does this change the scope of existing channels like #developers, #firefox-ci, etc.? Is #dev-help intended to be more of a “let’s get you routed to the right place” channel, or is it supposed to be the new place for all issues motivated by “I’m a developer that ran into problems with components I don’t have responsibility for?”

--
You received this message because you are subscribed to the Google Groups "dev-pl...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev-platform...@mozilla.org.
To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAAJAz%2B6TtZf%2BtTxro8MkKiRAgH-WvOWjBeP5ytYvyZBgSEn5Ng%40mail.gmail.com.

[Andrew Halberstadt]

More of the latter. If you know the specific team to reach out to and how to get help, I'd say continue going to those more specific channels. But if you don't know where to turn or no one is replying in those other channels, then #dev-help is there for that reason. One of the specific problems we're trying to solve is the case where you get bounced around a whole bunch of different channels either no one is able or willing to help. So instead of re-directing you, we'll try and pull expertise into #dev-help (if they aren't already there). Though, if we're unable to do that, redirection is still an option :)