You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Andrew Phillips <ap...@qrmedia.com> on 2014/01/10 23:53:58 UTC
Re: notifications@ and/or commits@ lists?
Just to resurrect this one, after seeing an interesting comment [1] in
a podling review about how a low signal-to-noise ratio on the dev@
list could also deter committers.
According to infra, we should just be able to file a ticket:
17:47] <gmcdonald> up to the project to choose. 1. create a
notfications list and keep issues or 2. rename and get all stuff go to
notifications.
[17:47] <gmcdonald> it is easy to rename a list
[17:48] <gmcdonald> we'd then need to tell jira the new name
[17:48] <andrewp> Good to hear. That's the option we were planning to
go for, as per http://markmail.org/message/jvkcwfk6psk24at5
[17:48] <gmcdonald> ok
[17:48] <andrewp> But somehow we didn't file the right request, or something.
[17:48] <gmcdonald> create a ticket when you've decided
[17:48] <andrewp> Just an INFRA ticket?
[17:48] <gmcdonald> yep
[17:49] <andrewp> Will do, then...thanks!
[17:49] <gmcdonald> np
I'm about to go ahead and open this ticket. Next step would be [2]:
1) Rename issues@ to notifications@
3) Use notifications@ in place of dev@ for all JIRA, GitHub, BuildHive
and DEV@cloud alerts, as well as Disqus comments and the like
4) Leave it up to individual developers to sign up for notifications@,
i.e. *not* to subscribe dev@ to that list by default
Please ping if there are any objections!
ap
[1]
http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201312.mbox/%3C328877DC-E7A5-4785-AD89-96D8BB0EFE21%40classsoftware.com%3E
[2] http://markmail.org/message/xfiax4wawe6xxcdu
Re: notifications@ and/or commits@ lists?
Posted by Andrew Phillips <ap...@qrmedia.com>.
> I think I can, maybe?
Good to know, thanks. Let's see what happens to the JIRA issue and
take it from there..?
ap
Re: notifications@ and/or commits@ lists?
Posted by Andrew Bayer <an...@gmail.com>.
I think I can, maybe?
A.
On Fri, Jan 10, 2014 at 3:31 PM, Andrew Phillips <ap...@qrmedia.com>wrote:
> This is now:
>
> https://issues.apache.org/jira/browse/INFRA-7180
>
> If INFRA is unable to unsubscribe dev@ from the new list, does anyone
> know who here is a moderator who *could* do that?
>
> ap
>
Re: notifications@ and/or commits@ lists?
Posted by Andrew Phillips <ap...@qrmedia.com>.
This is now:
https://issues.apache.org/jira/browse/INFRA-7180
If INFRA is unable to unsubscribe dev@ from the new list, does anyone
know who here is a moderator who *could* do that?
ap
RE: notifications@ and/or commits@ lists?
Posted by Everett Toews <ev...@RACKSPACE.COM>.
+1
Everett
________________________________________
From: Ignasi Barrera [ignasi.barrera@gmail.com]
Sent: Friday, January 10, 2014 5:03 PM
To: <de...@jclouds.apache.org>
Subject: Re: notifications@ and/or commits@ lists?
+1!
On 11 January 2014 00:01, Andrew Gaul <ga...@apache.org> wrote:
> This will be a huge improvement. Thanks for taking on this task!
>
> On Fri, Jan 10, 2014 at 11:53:58PM +0100, Andrew Phillips wrote:
>> Just to resurrect this one, after seeing an interesting comment [1] in a
>> podling review about how a low signal-to-noise ratio on the dev@ list could
>> also deter committers.
>>
>> According to infra, we should just be able to file a ticket:
>>
>> 17:47] <gmcdonald> up to the project to choose. 1. create a notfications
>> list and keep issues or 2. rename and get all stuff go to notifications.
>> [17:47] <gmcdonald> it is easy to rename a list
>> [17:48] <gmcdonald> we'd then need to tell jira the new name
>> [17:48] <andrewp> Good to hear. That's the option we were planning to go
>> for, as per http://markmail.org/message/jvkcwfk6psk24at5
>> [17:48] <gmcdonald> ok
>> [17:48] <andrewp> But somehow we didn't file the right request, or something.
>> [17:48] <gmcdonald> create a ticket when you've decided
>> [17:48] <andrewp> Just an INFRA ticket?
>> [17:48] <gmcdonald> yep
>> [17:49] <andrewp> Will do, then...thanks!
>> [17:49] <gmcdonald> np
>>
>> I'm about to go ahead and open this ticket. Next step would be [2]:
>>
>> 1) Rename issues@ to notifications@
>> 3) Use notifications@ in place of dev@ for all JIRA, GitHub, BuildHive and
>> DEV@cloud alerts, as well as Disqus comments and the like
>> 4) Leave it up to individual developers to sign up for notifications@,
>> i.e. *not* to subscribe dev@ to that list by default
>>
>> Please ping if there are any objections!
>>
>> ap
>>
>> [1] http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201312.mbox/%3C328877DC-E7A5-4785-AD89-96D8BB0EFE21%40classsoftware.com%3E
>> [2] http://markmail.org/message/xfiax4wawe6xxcdu
>
> --
> Andrew Gaul
> http://gaul.org/
Re: notifications@ and/or commits@ lists?
Posted by Ignasi Barrera <ig...@gmail.com>.
+1!
On 11 January 2014 00:01, Andrew Gaul <ga...@apache.org> wrote:
> This will be a huge improvement. Thanks for taking on this task!
>
> On Fri, Jan 10, 2014 at 11:53:58PM +0100, Andrew Phillips wrote:
>> Just to resurrect this one, after seeing an interesting comment [1] in a
>> podling review about how a low signal-to-noise ratio on the dev@ list could
>> also deter committers.
>>
>> According to infra, we should just be able to file a ticket:
>>
>> 17:47] <gmcdonald> up to the project to choose. 1. create a notfications
>> list and keep issues or 2. rename and get all stuff go to notifications.
>> [17:47] <gmcdonald> it is easy to rename a list
>> [17:48] <gmcdonald> we'd then need to tell jira the new name
>> [17:48] <andrewp> Good to hear. That's the option we were planning to go
>> for, as per http://markmail.org/message/jvkcwfk6psk24at5
>> [17:48] <gmcdonald> ok
>> [17:48] <andrewp> But somehow we didn't file the right request, or something.
>> [17:48] <gmcdonald> create a ticket when you've decided
>> [17:48] <andrewp> Just an INFRA ticket?
>> [17:48] <gmcdonald> yep
>> [17:49] <andrewp> Will do, then...thanks!
>> [17:49] <gmcdonald> np
>>
>> I'm about to go ahead and open this ticket. Next step would be [2]:
>>
>> 1) Rename issues@ to notifications@
>> 3) Use notifications@ in place of dev@ for all JIRA, GitHub, BuildHive and
>> DEV@cloud alerts, as well as Disqus comments and the like
>> 4) Leave it up to individual developers to sign up for notifications@,
>> i.e. *not* to subscribe dev@ to that list by default
>>
>> Please ping if there are any objections!
>>
>> ap
>>
>> [1] http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201312.mbox/%3C328877DC-E7A5-4785-AD89-96D8BB0EFE21%40classsoftware.com%3E
>> [2] http://markmail.org/message/xfiax4wawe6xxcdu
>
> --
> Andrew Gaul
> http://gaul.org/
Re: notifications@ and/or commits@ lists?
Posted by Andrew Gaul <ga...@apache.org>.
This will be a huge improvement. Thanks for taking on this task!
On Fri, Jan 10, 2014 at 11:53:58PM +0100, Andrew Phillips wrote:
> Just to resurrect this one, after seeing an interesting comment [1] in a
> podling review about how a low signal-to-noise ratio on the dev@ list could
> also deter committers.
>
> According to infra, we should just be able to file a ticket:
>
> 17:47] <gmcdonald> up to the project to choose. 1. create a notfications
> list and keep issues or 2. rename and get all stuff go to notifications.
> [17:47] <gmcdonald> it is easy to rename a list
> [17:48] <gmcdonald> we'd then need to tell jira the new name
> [17:48] <andrewp> Good to hear. That's the option we were planning to go
> for, as per http://markmail.org/message/jvkcwfk6psk24at5
> [17:48] <gmcdonald> ok
> [17:48] <andrewp> But somehow we didn't file the right request, or something.
> [17:48] <gmcdonald> create a ticket when you've decided
> [17:48] <andrewp> Just an INFRA ticket?
> [17:48] <gmcdonald> yep
> [17:49] <andrewp> Will do, then...thanks!
> [17:49] <gmcdonald> np
>
> I'm about to go ahead and open this ticket. Next step would be [2]:
>
> 1) Rename issues@ to notifications@
> 3) Use notifications@ in place of dev@ for all JIRA, GitHub, BuildHive and
> DEV@cloud alerts, as well as Disqus comments and the like
> 4) Leave it up to individual developers to sign up for notifications@,
> i.e. *not* to subscribe dev@ to that list by default
>
> Please ping if there are any objections!
>
> ap
>
> [1] http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201312.mbox/%3C328877DC-E7A5-4785-AD89-96D8BB0EFE21%40classsoftware.com%3E
> [2] http://markmail.org/message/xfiax4wawe6xxcdu
--
Andrew Gaul
http://gaul.org/