[PROPOSAL] send automated emails to dev@diversity

[Naomi Slater <ns...@apache.org>]

(copying diversity@apache.org for the time being because I expect it will
take a few days for everyone to move over to dev@diversity.apache.org)

now that we have dev@ set up, I would like to propose that we start sending
automated emails to the list

this is fairly standard practice at the ASF (although not ubiquitous) and
makes dev@ the hub of activity for our collective oversight

specifically, at the moment:

- automated emails from our JIRA project
- automated emails from our wiki

I am not too familiar with how Pelican works (the system that will power
our website at diversity.apache.org) but if there are changeset emails or
such like, I propose we send copies to dev@

I also propose that any Git projects we might end up using send copies of
automated emails to dev@

anything else I'm missing?

Re: [PROPOSAL] send automated emails to dev@diversity

[Griselda Cuevas <gr...@google.com.INVALID>]

I'd add GitHub.

On Wed, May 29, 2019, 3:44 AM Naomi Slater <ns...@apache.org> wrote:

> (copying diversity@apache.org for the time being because I expect it will
> take a few days for everyone to move over to dev@diversity.apache.org)
>
> now that we have dev@ set up, I would like to propose that we start
> sending
> automated emails to the list
>
> this is fairly standard practice at the ASF (although not ubiquitous) and
> makes dev@ the hub of activity for our collective oversight
>
> specifically, at the moment:
>
> - automated emails from our JIRA project
> - automated emails from our wiki
>
> I am not too familiar with how Pelican works (the system that will power
> our website at diversity.apache.org) but if there are changeset emails or
> such like, I propose we send copies to dev@
>
> I also propose that any Git projects we might end up using send copies of
> automated emails to dev@
>
> anything else I'm missing?
>