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 onl
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
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 st
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 h
Hi,
As the owner of the mentioned bot, I feel I need to jump in, not because
I want to defend any position (I pretty much don't care whether pulsebot
sends its messages to #developers or somewhere else), but just to
mention some facts.
Pulsebot did its first post to #developers on May 30, 2014, b
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),
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 cha
sides any pulsebot chatter). I think removing pulsebot
will just make it... deader. :-)
~ Gijs
On 04/11/2017 19:38, 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. Bu
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
#
+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 wrote:
> On 04/11/17 17:21, Zibi Braniecki wrote:
>>
>> +1
>>
>> The only thing I'd like to see from pulsebot on developers is:
>>
>>
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 people t
+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/listinfo/d
+1. I would love pulsebot to get it's own channel I can get mention alerts
on, and have developers just be development chat.
On Nov 4, 2017 8:13 AM, "Kartikaya Gupta" wrote:
> +1. I also find myself less likely to read the backscroll because of the
> high volume of pulsebot messages.
>
> Thanks
+1. I also find myself less likely to read the backscroll because of the
high volume of pulsebot messages.
Thanks for bringing this up!
On Nov 4, 2017 07:45, "Philipp Kewisch" wrote:
> Hey Folks,
>
> I'm a big fan of having development discussions in the open, and in the
> past #developers has
Hey Folks,
I'm a big fan of having development discussions in the open, and in the
past #developers has been the prime place to do that. Even if the
benefit may not be apparent vs. having a private discussion or using a
closed channel, I think this is one of many ways to increase interest
within t
15 matches
Mail list logo
