Re: Pulsebot in #developers

2017-11-06 Thread Nicolas B. Pierron
PM, Kris Maglione wrote: For what it's worth, I quite like having pulsebot in #developers. I'll admit the channel feels different since pulsebot started reporting there. But I've also seen a lot of discussions started based on some commit it reported. And a lot of the time, I only even think

Re: Pulsebot in #developers

2017-11-06 Thread David Major
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

Re: Pulsebot in #developers

2017-11-06 Thread Gijs Kruitbosch
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

Re: Pulsebot in #developers

2017-11-06 Thread Philipp Kewisch
On 11/5/17 12:55 PM, Mike Hommey wrote: > So it seems to me the core problem is not as much "there's too much noise" > as "people are not posting on #developers anymore". One could think > there's correlation, but I think the reality is simply that less people > use irc. Thanks for the stats and

Re: Pulsebot in #developers

2017-11-06 Thread Mike Hommey
hen pulsebot sends another dozen messages due to > checkins and merges. How much exactly becomes apparent when you visit > https://mozilla.logbot.info/developers/stats : pulsebot has said more > than twice as much as anyone else. > > Of course you could say, why don't I just

Re: Pulsebot in #developers

2017-11-06 Thread Gijs Kruitbosch
On 06/11/2017 00:23, zbranie...@mozilla.com wrote: but please, be careful because #developers is also the most natural channel for any newcomers to go to in order to ask entry level questions about our codebase. No, that should be (and is and has been for a considerable amount of time, IME),

Re: Pulsebot in #developers

2017-11-05 Thread zbraniecki
W dniu niedziela, 5 listopada 2017 08:18:37 UTC-8 użytkownik Gijs Kruitbosch napisał: > More generally, in response to Philipp's points, I'm not convinced > pulsebot is responsible for any decrease in responsiveness. Early in the > day here in Europe (ie when it's night in the Americas) the

Re: Pulsebot in #developers

2017-11-05 Thread Gijs Kruitbosch
rder which is too slow). On 04/11/2017 16:38, Simon Sapin wrote: > On 04/11/17 17:21, Zibi Braniecki wrote: >> The only thing I'd like to see from pulsebot on developers is: >> >> "26 commits have been merged from autoland into mozilla-central. >> List:http://...; >

Re: Pulsebot in #developers

2017-11-04 Thread Kris Maglione
For what it's worth, I quite like having pulsebot in #developers. I'll admit the channel feels different since pulsebot started reporting there. But I've also seen a lot of discussions started based on some commit it reported. And a lot of the time, I only even think to check #developers when

Re: Pulsebot in #developers

2017-11-04 Thread Tim Taubert
+1 A separate channel sounds like a great idea. And it will help dealing with two very different kinds of information. On Sat, Nov 4, 2017 at 5:38 PM, Simon Sapin <simon.sa...@exyr.org> wrote: > On 04/11/17 17:21, Zibi Braniecki wrote: >> >> +1 >> >> The only th

Re: Pulsebot in #developers

2017-11-04 Thread Simon Sapin
On 04/11/17 17:21, Zibi Braniecki wrote: +1 The only thing I'd like to see from pulsebot on developers is: "26 commits have been merged from autoland into mozilla-central. List:http://...; Even that would probably be still be high traffic. A separate channel would allow interested p

Re: Pulsebot in #developers

2017-11-04 Thread Zibi Braniecki
+1 The only thing I'd like to see from pulsebot on developers is: "26 commits have been merged from autoland into mozilla-central. List: http://...; zb. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/lis

Re: Pulsebot in #developers

2017-11-04 Thread Tom Ritter
n in the way" of this is pulsebot. I > > acknowledge the usefulness of getting notifications on checkin, but it > > does add a lot of noise to #developers. Questions asked or discussions > > quickly fade away when pulsebot sends another dozen messages due to > > checkin

Re: Pulsebot in #developers

2017-11-04 Thread Kartikaya Gupta
way" of this is pulsebot. I > acknowledge the usefulness of getting notifications on checkin, but it > does add a lot of noise to #developers. Questions asked or discussions > quickly fade away when pulsebot sends another dozen messages due to > checkins and merges. How much exactl

Pulsebot in #developers

2017-11-04 Thread Philipp Kewisch
ly becomes apparent when you visit https://mozilla.logbot.info/developers/stats : pulsebot has said more than twice as much as anyone else. Of course you could say, why don't I just ignore pulsebot? The point is that only few will actually do so. My impression over time is that less of the questi