I'd like a issues@avro or notifications@avro that has the detailed messages from Github and Jira. Great suggestion.
I would prefer PR and jira issue creation / closure still go to the dev list, but I don't feel strongly about it since I will probably subscribe to both lists. On Thu, May 7, 2020 at 8:08 AM Driesprong, Fokko <fo...@driesprong.frl> wrote: > Yes, I'd be in favor of having a separate ML. If you want to keep track of > the action at the repository, you can also get notified using Github. > > Cheers, Fokko > > Op do 7 mei 2020 om 14:37 schreef Ismaël Mejía <ieme...@gmail.com>: > > > Let's wait for others opinions and if we agree I will proceed to > > create the ML next week. > > > > On Thu, May 7, 2020 at 12:13 PM Ryan Skraba <r...@skraba.com> wrote: > > > > > > I think it's safe to create issues@ and merge the PR right away -- it > > > would pretty much restore the behaviour the dev@ list had at the > > > beginning of the year. > > > > > > I have all my mailing lists dumped into the same folder, but if > > > issues@ existed for JIRA and Github notifications, I would be tempted > > > to subscribe to the daily digest instead. > > > > > > I'm curious about how other highly-productive Apache developers have > > > their email filters set up for various projects! It's easy to get > > > overwhelmed by the volume (especially if you don't keep up daily, I > > > was off most of March/April). > > > > > > In any case, https://github.com/apache/avro/pull/873 LGTM! > > > > > > Ryan > > > > > > > > > Ryan > > > > > > On Wed, May 6, 2020 at 11:51 PM Ismaël Mejía <ieme...@gmail.com> > wrote: > > > > > > > > Other alternative (probably the cleanest is to let dev@ only for > > > > discussion and issues for all the JIRA/github action. The tradeoff > > > > there is that people subscribed to dev@ only may miss part of the > > > > action (+ it is not backwards compatible with our archives) but it is > > > > clearly an option too. > > > > > > > > On Wed, May 6, 2020 at 11:47 PM Ismaël Mejía <ieme...@gmail.com> > > wrote: > > > > > > > > > > The issues in the yaml file are every comment done on every issue > or > > > > > pull requests on github (notice that the issues part probably won't > > > > > apply to us since we use JIRA to track issues). > > > > > > > > > > Currently we receive ALL JIRA notifications into dev@ we can > change > > > > > that us well since it probably makes sense.,However this is a > > > > > different process of the .asf.yaml file. > > > > > > > > > > The proposed notification schema will still notify new PRs and > closed > > > > > PRs into dev@ which is valuable for awareness on new > contributions, > > > > > maybe we can do that for JIRA too, just notify on created and > closed > > > > > JIRAs (assuming INFRA can map such rule). then people interested in > > > > > tracking the middle steps and issue/PR discussions could go and > > > > > subscribe into issues@ where all the detailed information will be. > > > > > > > > > > Other opinions? Suggestions? > > > > > > > > > > > > > > > So many options > > > > > > > > > > On Wed, May 6, 2020 at 4:18 PM Ryan Skraba <r...@skraba.com> > wrote: > > > > > > > > > > > > This sounds good to me! The "issues" in the yaml are the GitHub > > > > > > issues, which are disabled in github right? > > > > > > > > > > > > Any opinions on moving JIRA notifications from j...@apache.org > to > > > > > > issues@ as well? That's what I would expect! > > > > > > > > > > > > I guess this would make little difference to me in practice > since I > > > > > > would subscribe to both, but it would make it a lot easier to > > browse > > > > > > and link to the dev@ mailing list on the web! > > > > > > > > > > > > All my best, Ryan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, May 6, 2020 at 1:15 AM Andy Le <anhl...@gmail.com> > wrote: > > > > > > > > > > > > > > Hi Ismaël, > > > > > > > > > > > > > > Yep, I think it's a little bit noisy for our mailing list with > > such notifications. But it's fun to see what other people are working on. > > > > > > > > > > > > > > IMHO, in addition to a new mailing list, we should have a > better > > label mechanism for easily routing/filtering messages. > > > > > > > > > > > > > > Thank you. > > > > > > > > > > > > > > On 2020/05/05 22:59:59, Ismaël Mejía <ieme...@gmail.com> > wrote: > > > > > > > > Hello, > > > > > > > > > > > > > > > > Some of you have probably noticed that we are receiving a LOT > > of extra > > > > > > > > notifications that were not active in the past. This is > > happening because > > > > > > > > Apache INFRA installed a new way to map notifications into > > mailing lists for its > > > > > > > > projects and the default configuration right now is sending > > all the github > > > > > > > > notifications to dev@ > > > > > > > > > > > > > > > > https://gitbox.apache.org/schemes.cgi?avro > > > > > > > > > > > > > > > > So I would like to propose that we create a new mailing list > > called maybe > > > > > > > > iss...@avro.apache.org To send all the git individual PR > > comments/reviews there > > > > > > > > and only the new/close PRs here. > > > > > > > > > > > > > > > > I suppose that issues@ could be a list of interest for some > > people and it will > > > > > > > > help us have a more readable dev@ mailing list. > > > > > > > > > > > > > > > > Technically all we need to do is create the new ML on > > selfserve and a new > > > > > > > > .asf.yaml file following this format. > > > > > > > > > > > > > > > > https://s.apache.org/asfyaml-notify > > > > > > > > > > > > > > > > WDYT? Other preferences or other name for the mailing list > > github@ maybe? > > > > > > > > More configuration ideas? > > > > > > > > > > > > > > > > You can see a WIP of the proposed changes here: > > > > > > > > https://github.com/apache/avro/pull/873 > > > > > > > > > > >
