Anyone who’s subscribe to any of core trac or wp-svn knows that there is a lot that’s getting sent around to inboxes everywhere. Most likely you have your own inbox/email rules setup so you don’t drown in some of the information and data-flow that can be quite large at times.
Although there is already a decent of signal-to-noise ratio, to a certain extent this is just part of being subscribed to those hoses and there’s very little you can do about it. This is why it’s pretty important that those that manage and oversee those distros and lists keep them clean and provide refined channels to subscribe to, if possible.
Andrew Nacin, in a recent post, shares some of his thoughts on a revision that he’s considering that might make more than just a few happy:
One of the original goals of bumpbot was to reduce the noise when doing code review on a commit that involved JS or CSS. But these commits can occur fairly often and still cause noise.
The concern is two-fold:
- Will skipped commit numbers cause people to look around for them, so instead of saving time, it actually increases time spent on these?
- If a bot screws up and no one is around to hear it, does it make a sound?
He’s asking for suggestions on if anyone has any opinions on the matter. Again, you may already have some decent filtering rules but for those new to it and who haven’t created those it might be a much cleaner way of data delivery.
In addition to reducing any additional noise Andrew shares that better subs to trac tickets are coming as well, which also should be a win.