adding d...@diversity.apache.org properly this time. I made a typo in my first email CC line. please reply to this email with further replies so that the new list gets copies (and so you don't get "email address doesn't exist" messages)
On Wed, 29 May 2019 at 13:03, Awasum Yannick <awa...@apache.org> wrote: > +1 > > On Wed, May 29, 2019 at 12:02 PM Myrle Krantz <my...@apache.org> wrote: > > > +1 > > > > On Wed, May 29, 2019 at 12:53 PM Naomi Slater <n...@tumbolia.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 d...@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? > > > > > >
