I agree with Kris' points.
Perhaps there's some kind of middle ground possible? Maybe if pulsebot
reported landed patch author + reviewer names (to keep the mentions) on
the hour every hour, with a link to pushlogs, or something. And all the
merges were coalesced to "autoland and inbound were merged to
mozilla-central, <link>" (wait 15 minutes before reporting any merges so
it can report them only once). Feels like that would drastically reduce
the number of messages, but keep useful functionality (like finding out
if there was a recent merge without loading all of treeherder 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://...";
>
> Even that would probably be still be high traffic.
Not really. There are less than 5 merge points a day (usually more like
1-3; this last Friday, for instance, there was 1, where inbound and
autoland were merged in quick succession, and only 1 backout and a
ffxbld change, making a grand total of 4 pushes to m-c that day).
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 channel is
usually dead (besides 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. 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 I get a highlight from a commit I landed or reviewed,
and then stumble on some interesting topic.
That said, pre-pulsebot, #developers was not exactly easy to follow
either. There tended to be (and still tend to be, really) several
unrelated discussions going on at the same time (several of which
involved the same person or people) that were hard to follow unless you
were part of them from the start. These days, more of that discussion
tends to happen in area-specific channels like #content, #jsapi,
#fx-team, ... where it's easier to follow.
On Sat, Nov 04, 2017 at 12:44:32PM +0100, Philipp Kewisch wrote:
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 the community. Back when I got started with Mozilla as a
volunteer, I enjoyed reading discussions in #developers because they
allowed me to peek into things that Mozilla developers were working on,
and at times got me interested in the code that was being talked about.
One thing that has recently "gotten 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
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 ignore pulsebot? The point is
that only few will actually do so. My impression over time is that less
of the questions I have asked are being answered, and my suspicion is
that in part, people qualified to answer will just not see it in
scrollback between all the pulsebot messages.
Long story short, can we move pulsebot to a separate channel so that
people can opt-in to, and encourage people to discuss their Gecko
development topics in #developers again?
Philip
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
