Naomi Slater wrote on 2019-5-29 6:43AM EDT: > (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) (Replying to corrected list name as you noted) > > now that we have dev@ set up, I would like to propose that we start sending > automated emails to the list
ProTip: Apache committers can self-subscribe to lists via Whimsy: https://whimsy.apache.org/committers/subscribe (requires login) > 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 +1, good idea. > 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@ Pelican is just the templating/build system. The files will still be in a traditional SVN or git repository. Question: which do we want to use? > I also propose that any Git projects we might end up using send copies of > automated emails to dev@ > > anything else I'm missing? > -- - Shane Director & Member The Apache Software Foundation --------------------------------------------------------------------- To unsubscribe, e-mail: diversity-unsubscr...@apache.org For additional commands, e-mail: diversity-h...@apache.org
