Killing the gerrit to dev-list spam ...

[Bjoern Michaelsen]

Hi,

On Thu, May 02, 2013 at 02:31:21PM -0500, Norbert Thiebaud wrote:
> And I re-iterate my earlier question: what is left on the dev ML ?
> chatter without patches ?

Everything but gerrit-patches. I e.g. filter out the gerrit-mails and there
stays enough on the list: Manual patches, ESC discussions, 10000-feet view code
insight (the stuff that later leads to concrete patches). As a side-effect it
will make the digest of the dev-list something that is sensible.

> I would suggest to find a way to filter-put auto generated comment,
> due to gerrit (like 'has been rebased'... and most of the gerrit
> buildbot generated one... except the final 'result' one)

filter-put? Sorry, I dont understand what you are aiming for here.

> If one want a daily digest of a list, one can subscribe in that mode
> to that list.. no need to inflict one on everybody by default.

True. But a digest keeps some visibility of the gerrit activity on the dev list
without drowning it and I assume we can generate a far better custom digest
showing what is going on gerrit than a default mailman digest.

> PS: the idea of being able to post a comment in gerrit via the ML
> seems interesting. Not sure how to do that best and spam-free... but
> still that would be a nice improvement to the ML workflow (and make
> the [PATCH] message generated by gerrit more relevant... and in turn
> make it compeling to keep them in the regular dev ML

I agree that it is an interesting idea, although I dont know how much people
would actually be doing it. I dont see how it is an argument for not having a
separate ML for gerrit though -- people who love to work via email will
subscribe that list anyway, those how do not prefer to do everything via email
will not care about the ability to reply to a gerrit change being tied to a
changes-list.

Best,

Bjoern