Forget one thing, if separating list can keep active discussions and votes on top page, it would be valuable for me.
2016년 8월 12일 (금) 오전 8:16, Jungtaek Lim <[email protected]>님이 작성: > IMHO, all committers/PMCs need to be noticed for JIRA and Github > activities. > (Sometimes pull requests are submitted without having associated JIRA > issue as I did it yesterday. Actually I don't strictly think > committers/PMCs need to be noticed for all of pull request comments, but at > least need to be noticed for open/close pull request activities.) > > So separating list is only for contributors which would like to hear > about community activities but don't want to see the details (issue level), > and reducing duplication should be handled even though we can move JIRA / > Github activities out of dev@ list. > > I assume that adding JIRA work log doesn't send notification. If it is, > that's enough for me. Separating list is optional. > > - Jungtaek Lim (HeartSaVioR) > > > > 2016년 8월 12일 (금) 오전 6:20, Kyle Nusbaum <[email protected]>님이 > 작성: > >> If this other mailing list gets notified of all github activity (all >> comments, etc.), is that sufficient for being "archived" on ASF hardware? >> I'm assuming the ASF is hosting their own mail servers. >> I'd much rather have all github activity go to a mailing list for archive >> than go to jira and end up in the mailing list 4 times anyway. >> -- Kyle >> >> On Thursday, August 11, 2016 3:54 PM, P. Taylor Goetz < >> [email protected]> wrote: >> >> >> We don’t need a formal vote if we have a general consensus. >> This is an issue I’d like to see fixed since it drives me nuts and is >> amplified by the number of mailing lists I’m subscribed to. >> The requirement to link github pull request comments, etc. to JIRA >> originates from the ASF policy that all artifacts of the decision-making >> process (email, issues, etc.) be archived on ASF-controlled hardware. The >> linking of github activity to JIRA partly addressed that, but it’s not >> optimal (e.g. What happens when a PR isn’t linked to a JIRA?). >> Personally, I want to get notified of all JIRA and github activity, but >> what I don’t want is 4 copies of every notification. I have some email >> filters to help alleviate that, but it’s not a good solution. >> One short-term solution for those who don’t care about JIRA/GitHub >> traffic would be to setup [email protected] and funnel all generated mail >> there (that’s just an INFRA ticket followed by some patience). That won’t >> alleviate the issue of duplicates for those that subscribe to that list. >> Another option that’s available now (it wasn’t in the past) is to switch >> over to github issues and stop using JIRA. Then people could set their own >> notification preferences in github. The downside is to close issues, it >> would require a git commit (the same mechanism we use today to close >> abandoned pull requests). Another downside is that issues would be >> read-only, so we wouldn’t be able to add labels, etc. >> Actually as I was typing this I was also chatting with INFRA about it. >> And it turns out you can funnel github activity into the work log for a >> JIRA, rather than comments. That will eliminate the duplicate emails. >> So it seems the solution might be: >> 1. Funnel github activity to the associated JIRA work log.2. setup >> [email protected]. and route JIRA notification to that. >> That would keep dev@ clear of the machines. ;) How does that sound? >> -Taylor >> >> >> On Aug 11, 2016, at 3:08 PM, Kyle Nusbaum <[email protected]> >> wrote: >> I'm pro-getting-rid-of-github-messages-on-jira as well, but that's less >> annoying to me personally than the mails. It's also not clear what a better >> solution for keeping jira and github "linked" is at this point. >> As far as what notifications come through, once it's on its own list I >> don't care if everything comes through. >> Do we need to call an official vote or something to actually get this >> moving? I'm not sure what the procedure is for setting up mailing lists. >> -- Kyle >> >> On Thursday, August 11, 2016 9:18 AM, Jungtaek Lim <[email protected]> >> wrote: >> >> >> First of all we need to define which things are annoying. Belows are some >> which are mentioned one or more people, >> >> 1. Duplicated notifications per comment (You can receive 2 mails from dev@ >> + 1 mails from github up to condition (you're an author, you're watching, >> you're mentioned, etc) + occasionally 1 empty change mail from dev -> up >> to >> 4 mails) >> 2. Copied comments from JIRA issue (with or without notification) >> >> and also need to define which things should be notified >> >> a. open pull request and close pull request >> b. only open pull request (linking github pull request and notified by >> changing status of issue - we can have 'patch available' status for that) >> c. no we should receive all of comments (just need to reduce duplicated >> things) >> >> - Jungtaek Lim (HeartSaVioR) >> >> >> 2016년 8월 11일 (목) 오후 10:52, Bobby Evans <[email protected]>님이 >> 작성: >> >> >> Yes lets have a separate firehouse/commit/whatever mailing list that if >> people really want all of that data they can see it all. That way it is >> archived in ASF infra. I do see value in having JIRA and GITHUB linked, >> I'm not sure if there is a better way to link the two right now though. >> If >> someone does have experience with this type of thing and can make a better >> solution I think we can talk to INFRA about adopting/supporting those >> changes. - Bobby >> >> On Thursday, August 11, 2016 8:41 AM, Aditya Desai <[email protected]> >> wrote: >> >> >> Please reduce the number of emails. I am getting many many emails in >> recent >> days and spam my inbox. >> >> On Thu, Aug 11, 2016 at 2:41 AM, Erik Weathers < >> [email protected]> wrote: >> >> >> I will state again (as I've done on prior email threads) that I find no >> value in spamming the JIRA issues like this, and that I strongly believe >> that this behavior is in fact detrimental since it obscures the actual >> comments on the issue itself. The proposed solution of just moving the >> destination of the JIRA emails to a different list than >> [email protected] >> doesn't solve that root problem. >> >> I want to be able to read a JIRA issue without having to skim over dozens >> and dozens of auto-appended code review messages. I truly cannot >> understand why this isn't an annoyance for others. I could be really >> snarky and reformat this email to have a bunch of random stuff in between >> every sentence to make my point, but I hope this sentence suffices to >> >> prove >> >> it? >> >> Though I must acknowledge your point Jungtaek that there is some Apache >> policy that all code review comments need to be archived into some apache >> system. Maybe we can use the attachment functionality of JIRA instead of >> making these separate comments on the JIRA issue? I'm not sure how the >> integration is set up right now, that seems feasible. >> >> - Erik >> >> On Thu, Aug 11, 2016 at 2:08 AM, Matthias J. Sax <[email protected]> >> >> wrote: >> >> >> >> 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 <[email protected] >> >> d>님이 >> >> 작성: >> >> >> 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 >> >> >> >> >> >> >> >> >> >> >> >> -- >> Aditya Ramachandra Desai >> MS Computer Science Graduate Student >> USC Viterbi School of Engineering >> Los Angeles, CA 90007 >> M : +1-415-463-9864 | L : https://www.linkedin.com/in/adityardesai >> >> >> >> >> >> >> >> >> > >
