I like the idea of have one more mailing list to reduce load on dev-list. -Matthias
On 08/11/2016 11:07 AM, Jungtaek Lim wrote: > I remember that Taylor stated that all github comments should be copied to > somewhere Apache infra, and it's Apache JIRA for us. > > It seems to make sense but I'm curious other projects respect this rule. I > also subscribed dev list of Kafka, Zeppelin, Flink, HBase, Spark (although > I barely see them) but no project is sending mail per each comment. Some of > them copy github comments to JIRA issue but no notification, and others > doesn't even copy comments to JIRA issue. > (You can check this with dev mailing list archive, too.) > > I'm in favor of reducing simple notification mails. Personally I saw most > of Storm dev. mails so I'm fine to keep mailing as it is (with some > annoying 'empty' notification), but it can also be done with watching > Github project. > > This is not raised for the first time, and I would like to discuss > seriously and see the changes. > > Thanks, > Jungtaek Lim (HeartSaVioR) > > 2016년 8월 11일 (목) 오후 2:22, Kyle Nusbaum <knusb...@yahoo-inc.com.invalid>님이 > 작성: > >> There seems to be a surplus of automatically-generated emails on the dev >> mailing list. >> Github and Apache's Jira constantly send mails to the dev list. >> >> I'm not sure that anyone finds these useful. Even if they do, I wonder if >> its better to move them to a separate list. It's possible that everyone has >> email filters employed to sort this out, but if every subscriber has the >> same filters employed, it might indicate the need for a separate list. -- >> Kyle >
signature.asc
Description: OpenPGP digital signature
