Finally submitted - will let you all know when it's ready. I asked to
renamed issues@ to notifications@.

A.


On Fri, Sep 6, 2013 at 10:22 AM, Andrew Bayer <[email protected]>wrote:

> Aaaaaand was not able to due to crazy release hell here at work. I'll try
> again today!
>
> A.
>
>
> On Thu, Sep 5, 2013 at 7:09 AM, Andrew Bayer <[email protected]>wrote:
>
>> I'll try to get these started today.
>>
>> A.
>>
>>
>> On Wed, Sep 4, 2013 at 9:19 PM, Andrew Phillips <[email protected]>wrote:
>>
>>> Yep - any of the moderators can send a email to
>>>> [email protected].**org <[email protected]>and 
>>>> receive a list of all
>>>> subscribers.
>>>>
>>>
>>> Unfortunately, I don't have permissions to run those for issues@ or
>>> commits@ as I'm not a moderator of either, it seems.
>>>
>>> I was also all set to file a JIRA issue with INFRA, but according to the
>>> contact guide [1] it actually seems that only Members and Officers (incl.
>>> all PMC charis) can submit the relevant form.
>>>
>>> Do we have a list subscriber with suitable karma who could fill out this
>>> request?
>>>
>>> Specifically:
>>>
>>> * create [email protected]
>>> * subscribe notifications@ to commits@
>>> * unsubscribe dev@ from issues@, if currently subscribed
>>> * deactivate issues@ (if these two could be combined as a 'rename
>>> issues@ to notifications@' that would obviously be even easier)
>>> * modify the JCLOUDS JIRA config to email notifications@ instead of
>>> issues@ (unfortunately, I don't seem to have permissions to change that)
>>>
>>> We should be able to handle the remaining changes to DEV@cloud, GitHub
>>> and BuildHive.
>>>
>>> If there's anything I can do to expedite this process, please let me
>>> know!
>>>
>>> ap
>>>
>>> [1] 
>>> https://www.apache.org/dev/**infra-contact#how<https://www.apache.org/dev/infra-contact#how>
>>>
>>
>>
>

Reply via email to