Pulsebot in #developers
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
Re: Pulsebot in #developers
+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 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 > ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Pulsebot in #developers
+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 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 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 > > > ___ > 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
Re: Pulsebot in #developers
+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/dev-platform
Re: Pulsebot in #developers
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 to opt-in. -- Simon Sapin ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Pulsebot in #developers
+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: >> >> "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 to opt-in. > > -- > Simon Sapin > > ___ > 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
Re: Pulsebot in #developers
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
Re: TypeError: %d format: a number is required, not float when building Firefox 52.4.1esr in Linux from Scratch
> File > "/root/sources/firefox-52.4.1esr/toolkit/components/telemetry/gen-event-data.py", > line 82, in write_common_event_table > e.dataset), > TypeError: %d format: a number is required, not float I haven't come across this error before, nor did a quick search turn up anything. I would suggest filing a bug report in the Toolkit :: Telemetry component [1], and hopefully people more familiar with that code can point you in the right direction. > The system I'm building on has 2 1GHz Pentium III processors and 1GB of RAM. Note that you may have trouble linking Firefox on a system with 1 GB RAM. The build documentation says a minimum of 2 GB is required [2] (and I'm not even sure that that's up to date; the developer machines we build on in practice have >= 4 GB RAM). Cheers, Botond [1] https://bugzilla.mozilla.org/enter_bug.cgi?product=Toolkit&component=Telemetry [2] https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Linux_Prerequisites ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
