I use #developers for two things: 1. I prefer to keep my discussions in smaller topic channels, but for my sanity I also try to keep my channel list small. There is a large set of people whom I ping roughly once a month and can't be bothered matching channels with. #developers is my "lowest common denominator" for talking to those people.
2. To cast the widest possible net for immediate help with some sudden roadblock or unfamiliar tool etc. I don't really care whether pulsebot gets moved, but it won't change my use of #developers. On Mon, Nov 6, 2017 at 8:13 AM, Gijs Kruitbosch <gijskruitbo...@gmail.com> wrote: > On 06/11/2017 12:49, Philipp Kewisch wrote: > >> If there is a better place to ask ad-hoc questions about Gecko, I am >> happy to go there (and we should make sure the channel is promoted in >> our docs). >> > > I think different teams have ended up with different IRC channels, as Kris > said. Frontend Firefox stuff tends to go in #fx-team, and #content, #jsapi > and similar channels each cater to their own "niche", so to speak. > > I can see how less usage of IRC can lead to the situation we have now. >> As long as there is an (open) replacement that is more accepted nowadays >> I think this is fine, but aside from that I think we should find a way >> to promote discussing Firefox and Platform issues in the open again. >> > > I am not aware of people discussing Firefox or Platform *engineering* > issues in other places, open or otherwise. I am aware of incidental > non-engineering folks using Slack for bugreporting (unsurprisingly, a lot > of those questions get answered with "file a bug in bugzilla"), but it > seems to me that's not what you're talking about... > > ~ Gijs > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
