commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gilles <>
Subject Re: [All] Finer-grained MLs
Date Fri, 15 Dec 2017 15:59:08 GMT
On Fri, 15 Dec 2017 15:17:43 +0000, sebb wrote:
> On 15 December 2017 at 14:08, Gilles <> 
> wrote:
>> On Fri, 15 Dec 2017 12:13:12 +0100, Jochen Wiedmann wrote:
>>> [...]
>>> Could we have a mailing list, like,
>>> [...]
>> I'd like to expand the suggestion: make component-specific MLs for
>> automatically generated messages (GitHub, JIRA, Nexus) so that 
>> people
>> not actively involved in the development of <some component> are not
>> overwhelmed by posts that are always to be deleted (in which case it
>> is rather more efficient to avoid sending it in the first place).
> -1
> For the same reason that commit messages are of concern to all 
> Commons
> developers.

They are not if the only action is always "Move to trash".
Such messages are useful only to those who decide so.  They can be
subscribed to as many list they want.
Why should others be annoyed by pull requests notices if they are
never going to apply/read them?

Even worse, I receive some messages twice!
Sometimes there are so many of them that they are blocked by the ISP.
Hence I may be missing the one important (human-generated) message
because of the heap of information-less crap.

In case you did not notice, I'm not asking to split "dev"!
Only "issues".

The "concern" only applies to the assumption that committed code
is hopefully reviewed by (some of) the developers.
Or do I miss something? [We did not need nor used those automated
message for years... The flood of mails is not an improvement!]

> Such messages are easy enough to filter if required.

It is healthier to not emit pollution than to filter it.


>> Of course, this opt-out would not concern "commit" messages.
>> Gilles

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message