www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Phillips (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-7213) Allow 4 non-ASF email addresses to send to notifications@jclouds.apache.org
Date Thu, 23 Jan 2014 03:10:35 GMT

    [ https://issues.apache.org/jira/browse/INFRA-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879401#comment-13879401
] 

Andrew Phillips edited comment on INFRA-7213 at 1/23/14 3:09 AM:
-----------------------------------------------------------------

> A little further clarity perhaps, please?

Hi Tony! I'll hope I'll be able to catch you on #asfinfra tomorrow to discuss, but let me
also try to explain here:

TL;DR: the subset of core jclouds committers that is interested in these notifications is
considerably smaller than the membership of the dev list (<10 vs. 81 currently on the dev
list)

Detail:
Partly due to the many different clouds supported by jclouds, there are many "casual" contributors
on the dev list who do not track day-to-day activity of jclouds. There are also many development-related
questions from users who are looking to implement or configure jclouds in ways that go beyond
the scope of the user list.

For all these, the large number of CI, JIRA, commit and review notifications that until recently
went to the dev list are a considerable source of noise that has encouraged quite a few to
send jclouds dev emails straight to Trash. In order to prevent this, we're trying to increase
the signal-to-noise ratio by moving these notifications over to a list that likely only the
core committers will follow.

See the discussion at the thread above and http://markmail.org/thread/4s7spzsiyk45upce (esp.
http://markmail.org/message/6myydcsdxdy7p7iv) for examples. This quote:

"Also I have a suggestion as I found it hard to scan your dev mailing list as there's a lot
of review and JIRA emails being sent to the dev list.  You might want to consider moving them
to a separate issues list."

from a recent incubator report (http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201312.mbox/%3C328877DC-E7A5-4785-AD89-96D8BB0EFE21%40classsoftware.com%3E)
for a different project served as additional motivation.

Hope this helps clarify things!


was (Author: andrewp):
> A little further clarity perhaps, please?

Hi [~pctony]! I'll hope I'll be able to catch you on #asfinfra tomorrow to discuss, but let
me also try to explain here:

TL;DR: the subset of core jclouds committers that is interested in these notifications is
considerably smaller than the membership of the dev list (<10 vs. 81 currently on the dev
list)

Detail:
Partly due to the many different clouds supported by jclouds, there are many "casual" contributors
on the dev list who do not track day-to-day activity of jclouds. There are also many development-related
questions from users who are looking to implement or configure jclouds in ways that go beyond
the scope of the user list.

For all these, the large number of CI, JIRA, commit and review notifications that until recently
went to the dev list are a considerable source of noise that has encouraged quite a few to
send jclouds dev emails straight to Trash. In order to prevent this, we're trying to increase
the signal-to-noise ratio by moving these notifications over to a list that likely only the
core committers will follow.

See the discussion at the thread above and http://markmail.org/thread/4s7spzsiyk45upce (esp.
http://markmail.org/message/6myydcsdxdy7p7iv) for examples. This quote:

"Also I have a suggestion as I found it hard to scan your dev mailing list as there's a lot
of review and JIRA emails being sent to the dev list.  You might want to consider moving them
to a separate issues list."

from a recent incubator report (http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201312.mbox/%3C328877DC-E7A5-4785-AD89-96D8BB0EFE21%40classsoftware.com%3E)
for a different project served as additional motivation.

Hope this helps clarify things!

> Allow 4 non-ASF email addresses to send to notifications@jclouds.apache.org
> ---------------------------------------------------------------------------
>
>                 Key: INFRA-7213
>                 URL: https://issues.apache.org/jira/browse/INFRA-7213
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: Mailing Lists
>            Reporter: Andrew Phillips
>            Assignee: Gavin
>
> At jclouds, we are trying to reduce the "notification noise" on the dev list [1] by moving
builder and pull request review commit notifications to notifications@ (created in INFRA-7180).
> Specifically, we would need these four non-ASF addresses to be able to post to the list:
> - 'buildhive-github@cloudbees.com' (BuildHive)
> - 'jenkins-no-reply@cloudbees.com' (DEV@cloud)
> - 'notifications@github.com' and 'noreply@github.com' (GitHub)
> As per discussion with gmcdonald on IRC, creating a ticket to discuss this.
> [1] http://markmail.org/thread/56h7ranonrfqlukr



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message