All, Turns out the process is simpler:
A PMC member must create the lists using the self-management potal: selfserve.apache.org Once this is done someone can update the INFRA-15988 ticket and the folks will execute the changes. On Wed, Jan 31, 2018 at 12:15 AM, Otto Fowler <ottobackwa...@gmail.com> wrote: > We could also just skip ‘b’ and go directly to ‘c’ like apache-commons and > have > commits@ issues@. > > > > > On January 30, 2018 at 08:03:37, Andre (andre-li...@fucs.org) wrote: > > James, > > Give nobody opposed, I would suggest one of the PMCs contact the INFRA to > get this actioned. > > They would need to assist with: > > 1. Creation of the new "issues" list > 2. redirect both GitHub and JIRA integrations to the new list > > Cheers > > On Sat, Jan 27, 2018 at 9:40 AM, James Sirota <jsir...@apache.org> wrote: > > > Should we file an infra ticket on this? > > > > 19.01.2018, 13:56, "zeo...@gmail.com" <zeo...@gmail.com>: > > > I would give that +1 as well. > > > > > > Jon > > > > > > On Fri, Jan 19, 2018 at 3:32 PM Casey Stella <ceste...@gmail.com> > wrote: > > > > > >> I could get behind that. > > >> > > >> On Fri, Jan 19, 2018 at 3:31 PM, Andre <andre-li...@fucs.org> wrote: > > >> > > >> > Folks, > > >> > > > >> > May I suggest Metron follows the NiFi mailing list strategy (we got > > >> > inspired by another project but I don't recall the name) and remove > > the > > >> > github comments from the dev list? > > >> > > > >> > Within NiFi we have both the dev and the issues lists. dev is for > > humans, > > >> > issues is for JIRA and github commits.[1] > > >> > > > >> > This allows the list thread list to be cleaner and is particularly > > >> helpful > > >> > for those reading the list from a list aggregation service. > > >> > > > >> > Cheers > > >> > > > >> > > > >> > [1] https://lists.apache.org/list.html?iss...@nifi.apache.org > > >> > > > > > > > -- > > > > > > Jon > > > > ------------------- > > Thank you, > > > > James Sirota > > PMC- Apache Metron > > jsirota AT apache DOT org > > > > > >
