I second Kris on the fact that the main reason I go to #developer is because
of the reviewer / author ping that I get.
I am still looking into patches which are submitted when I am mentioned as a
reviewer, in case someone is pushing code without applying nits, or with
additional un-reviewed modifications.
As of today, I mostly used #developers as a hub to be redirected to the
right channels, such as #bugzilla, #ateam, #necko, … So the large volume of
pulsebot messages has never been something I really cared for.
Is #developers supposed to be used differently?
On 11/04/2017 07:38 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 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
--
Nicolas B. Pierron
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
