> The other option would be to somehow subscribe dev@ through the standard > GitHub watcher framework by making it the notification address
jclouds does that for the jclouds-mirror user (which is the one that periodically mirrors the ASF Git repos which are the source of truth to GitHub). See http://mail-archives.apache.org/mod_mbox/jclouds-notifications/201402.mbox/browser We recently decided to send these emails to notifications@ rather than dev@, because, like Matei, all committers are already watching the GitHub repos and end up getting lots of duplicate emails. Subscribers to the dev@ list were also complaining about the signal-to-noise ratio. [1, 2] ap [1] http://markmail.org/message/4s7spzsiyk45upce [2] https://issues.apache.org/jira/browse/INFRA-7213
