The new "issues" list has been created. My original plan was to import the current "dev" list into "issues", but INFRA recommended against it, favoring folks signing up directly instead (which seems reasonable to me).
To subscribe just send an email to: issues-subscr...@shiro.apache.org I have a couple of tiny PRs related to this to keep the ball rolling: Configure JIRA messages to go to the "issues" list https://github.com/apache/shiro/pull/307 Add the "issues" mailing list link to the site https://github.com/apache/shiro-site/pull/84 On Thu, Jun 17, 2021 at 11:28 PM Jean-Baptiste Onofre <j...@nanthrax.net> wrote: > +1 > > Regards > JB > > > Le 16 juin 2021 à 19:38, Brian Demers <brian.dem...@gmail.com> a écrit : > > > > I'm going to split the current dev list and auto add current > `dev@shiro.a.o` > > subscribers to a new `iss...@shiro.apache.org` > > (from there everyone will be able to manage how they want those messages > > delivered) > > > > Assuming I don't hear any objections ;) > > > > On Thu, May 27, 2021 at 6:05 AM Francois Papon < > francois.pa...@openobject.fr> > > wrote: > > > >> big +1 :) > >> > >> regards, > >> > >> François > >> fpa...@apache.org > >> > >> Le 26/05/2021 à 23:54, Brian Demers a écrit : > >>> Currently, both JIRA and Gitbox notifications are sent to the dev list > >>> (current traffic): > >>> > https://mail-archives.apache.org/mod_mbox/shiro-dev/202105.mbox/browser > >>> > >>> I propose moving the GitHub/Gitbox notifications to only > >>> comm...@shiro.apache.org > >>> > >>> And move JIRA notifications to a new `iss...@shiro.apache.org` list. > >>> > >>> > >>> The goal is to allow folks more fine-grained control over email > >>> notifications from the project. Maybe you want to get commit > >> notifications > >>> from GitHub directly, or maybe you want to apply labels to your mail > >> based > >>> on the list name. This change should allow for the same level of > >>> notifications we have today (if you want that), or minimize your > >>> notifications if you wish. > >>> > >>> > >>> Does anyone have any strong feelings on the topic (or alternative > >>> suggestions)? > >>> > >>> > >>> Implementation note: > >>> > >>> We should be able to update these settings with a simple PR: > >>> https://github.com/apache/shiro/blob/main/.asf.yaml > >>> > >>> (Commits are actually configured go to commits@, so I'm actually not > >> sure > >>> why they are currently going to dev@ as well) > >>> > >>> More info on the `.asf.yaml` > >>> > >> > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-BranchProtection > >>> > >> > >
