You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metron.apache.org by Andre <an...@fucs.org> on 2018/03/19 12:16:43 UTC
Re: [DISCUSS] Time to remove github updates from dev?
Folks,
All rejoice. This has been finally implemented.
Cheers
On 7 Feb 2018 08:33, "Andre" <an...@fucs.org> wrote:
> 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 <ot...@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-lists@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 <js...@apache.org>
>> wrote:
>>
>> > Should we file an infra ticket on this?
>> >
>> > 19.01.2018, 13:56, "Zeolla@GMail.com" <ze...@gmail.com>:
>> > > I would give that +1 as well.
>> > >
>> > > Jon
>> > >
>> > > On Fri, Jan 19, 2018 at 3:32 PM Casey Stella <ce...@gmail.com>
>> wrote:
>> > >
>> > >> I could get behind that.
>> > >>
>> > >> On Fri, Jan 19, 2018 at 3:31 PM, Andre <an...@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?issues@nifi.apache.org
>> > >> >
>> > >
>> > > --
>> > >
>> > > Jon
>> >
>> > -------------------
>> > Thank you,
>> >
>> > James Sirota
>> > PMC- Apache Metron
>> > jsirota AT apache DOT org
>> >
>> >
>>
>>
>
Re: [DISCUSS] Time to remove github updates from dev?
Posted by Simon Elliston Ball <si...@simonellistonball.com>.
Should we not add the new lists to the website?
Simon
> On 19 Mar 2018, at 14:02, Casey Stella <ce...@gmail.com> wrote:
>
> +1
>
>
> On Mon, Mar 19, 2018 at 8:16 AM Andre <an...@fucs.org> wrote:
>
>> Folks,
>>
>> All rejoice. This has been finally implemented.
>>
>> Cheers
>>
>> On 7 Feb 2018 08:33, "Andre" <an...@fucs.org> wrote:
>>
>>> 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 <ot...@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-lists@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 <js...@apache.org>
>>>> wrote:
>>>>
>>>>> Should we file an infra ticket on this?
>>>>>
>>>>> 19.01.2018, 13:56, "Zeolla@GMail.com" <ze...@gmail.com>:
>>>>>> I would give that +1 as well.
>>>>>>
>>>>>> Jon
>>>>>>
>>>>>> On Fri, Jan 19, 2018 at 3:32 PM Casey Stella <ce...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>>> I could get behind that.
>>>>>>>
>>>>>>> On Fri, Jan 19, 2018 at 3:31 PM, Andre <an...@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?issues@nifi.apache.org
>>>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Jon
>>>>>
>>>>> -------------------
>>>>> Thank you,
>>>>>
>>>>> James Sirota
>>>>> PMC- Apache Metron
>>>>> jsirota AT apache DOT org
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
Re: [DISCUSS] Time to remove github updates from dev?
Posted by Casey Stella <ce...@gmail.com>.
+1
On Mon, Mar 19, 2018 at 8:16 AM Andre <an...@fucs.org> wrote:
> Folks,
>
> All rejoice. This has been finally implemented.
>
> Cheers
>
> On 7 Feb 2018 08:33, "Andre" <an...@fucs.org> wrote:
>
> > 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 <ot...@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-lists@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 <js...@apache.org>
> >> wrote:
> >>
> >> > Should we file an infra ticket on this?
> >> >
> >> > 19.01.2018, 13:56, "Zeolla@GMail.com" <ze...@gmail.com>:
> >> > > I would give that +1 as well.
> >> > >
> >> > > Jon
> >> > >
> >> > > On Fri, Jan 19, 2018 at 3:32 PM Casey Stella <ce...@gmail.com>
> >> wrote:
> >> > >
> >> > >> I could get behind that.
> >> > >>
> >> > >> On Fri, Jan 19, 2018 at 3:31 PM, Andre <an...@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?issues@nifi.apache.org
> >> > >> >
> >> > >
> >> > > --
> >> > >
> >> > > Jon
> >> >
> >> > -------------------
> >> > Thank you,
> >> >
> >> > James Sirota
> >> > PMC- Apache Metron
> >> > jsirota AT apache DOT org
> >> >
> >> >
> >>
> >>
> >
>
Re: [DISCUSS] Time to remove github updates from dev?
Posted by Anand Subramanian <as...@hortonworks.com>.
Just to close loop on this.. the PR was merged and the website is up-to-date as well.
Thanks,
Anand
On 4/5/18, 10:34 AM, "Anand Subramanian" <as...@hortonworks.com> wrote:
I have created https://github.com/apache/metron/pull/981
Regards
Anand
On 4/4/18, 11:44 PM, "Nick Allen" <ni...@nickallen.org> wrote:
I updated the Wiki. We should probably also update the main web, but I
have not done that.
https://cwiki.apache.org/confluence/display/METRON/Community+Resources#CommunityResources-JointheCommunity-GetingStarted
On Wed, Apr 4, 2018 at 1:55 PM, Simon Elliston Ball <
simon@simonellistonball.com> wrote:
> I would say we should also update our website with subscription
> information.
>
> Simon
>
> > On 4 Apr 2018, at 18:51, Nick Allen <ni...@nickallen.org> wrote:
> >
> > https://lists.apache.org/list.html?issues@metron.apache.org
> >
> > On Tue, Mar 20, 2018 at 5:06 PM, Otto Fowler <ot...@gmail.com>
> > wrote:
> >
> >> How about a link?
> >>
> >>
> >>
> >> On March 19, 2018 at 08:16:46, Andre (andre-lists@fucs.org) wrote:
> >>
> >> Folks,
> >>
> >> All rejoice. This has been finally implemented.
> >>
> >> Cheers
> >>
> >> On 7 Feb 2018 08:33, "Andre" <an...@fucs.org> wrote:
> >>
> >>> 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 <ottobackwards@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-lists@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 <js...@apache.org>
> >> wrote:
> >>>>
> >>>>> Should we file an infra ticket on this?
> >>>>>
> >>>>> 19.01.2018, 13:56, "Zeolla@GMail.com" <ze...@gmail.com>:
> >>>>>> I would give that +1 as well.
> >>>>>>
> >>>>>> Jon
> >>>>>>
> >>>>>> On Fri, Jan 19, 2018 at 3:32 PM Casey Stella <ce...@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>>> I could get behind that.
> >>>>>>>
> >>>>>>> On Fri, Jan 19, 2018 at 3:31 PM, Andre <an...@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?issues@nifi.apache.org
> >>>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>>
> >>>>>> Jon
> >>>>>
> >>>>> -------------------
> >>>>> Thank you,
> >>>>>
> >>>>> James Sirota
> >>>>> PMC- Apache Metron
> >>>>> jsirota AT apache DOT org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>
>
>
Re: [DISCUSS] Time to remove github updates from dev?
Posted by Anand Subramanian <as...@hortonworks.com>.
I have created https://github.com/apache/metron/pull/981
Regards
Anand
On 4/4/18, 11:44 PM, "Nick Allen" <ni...@nickallen.org> wrote:
I updated the Wiki. We should probably also update the main web, but I
have not done that.
https://cwiki.apache.org/confluence/display/METRON/Community+Resources#CommunityResources-JointheCommunity-GetingStarted
On Wed, Apr 4, 2018 at 1:55 PM, Simon Elliston Ball <
simon@simonellistonball.com> wrote:
> I would say we should also update our website with subscription
> information.
>
> Simon
>
> > On 4 Apr 2018, at 18:51, Nick Allen <ni...@nickallen.org> wrote:
> >
> > https://lists.apache.org/list.html?issues@metron.apache.org
> >
> > On Tue, Mar 20, 2018 at 5:06 PM, Otto Fowler <ot...@gmail.com>
> > wrote:
> >
> >> How about a link?
> >>
> >>
> >>
> >> On March 19, 2018 at 08:16:46, Andre (andre-lists@fucs.org) wrote:
> >>
> >> Folks,
> >>
> >> All rejoice. This has been finally implemented.
> >>
> >> Cheers
> >>
> >> On 7 Feb 2018 08:33, "Andre" <an...@fucs.org> wrote:
> >>
> >>> 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 <ottobackwards@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-lists@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 <js...@apache.org>
> >> wrote:
> >>>>
> >>>>> Should we file an infra ticket on this?
> >>>>>
> >>>>> 19.01.2018, 13:56, "Zeolla@GMail.com" <ze...@gmail.com>:
> >>>>>> I would give that +1 as well.
> >>>>>>
> >>>>>> Jon
> >>>>>>
> >>>>>> On Fri, Jan 19, 2018 at 3:32 PM Casey Stella <ce...@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>>> I could get behind that.
> >>>>>>>
> >>>>>>> On Fri, Jan 19, 2018 at 3:31 PM, Andre <an...@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?issues@nifi.apache.org
> >>>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>>
> >>>>>> Jon
> >>>>>
> >>>>> -------------------
> >>>>> Thank you,
> >>>>>
> >>>>> James Sirota
> >>>>> PMC- Apache Metron
> >>>>> jsirota AT apache DOT org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>
>
>
Re: [DISCUSS] Time to remove github updates from dev?
Posted by Nick Allen <ni...@nickallen.org>.
I updated the Wiki. We should probably also update the main web, but I
have not done that.
https://cwiki.apache.org/confluence/display/METRON/Community+Resources#CommunityResources-JointheCommunity-GetingStarted
On Wed, Apr 4, 2018 at 1:55 PM, Simon Elliston Ball <
simon@simonellistonball.com> wrote:
> I would say we should also update our website with subscription
> information.
>
> Simon
>
> > On 4 Apr 2018, at 18:51, Nick Allen <ni...@nickallen.org> wrote:
> >
> > https://lists.apache.org/list.html?issues@metron.apache.org
> >
> > On Tue, Mar 20, 2018 at 5:06 PM, Otto Fowler <ot...@gmail.com>
> > wrote:
> >
> >> How about a link?
> >>
> >>
> >>
> >> On March 19, 2018 at 08:16:46, Andre (andre-lists@fucs.org) wrote:
> >>
> >> Folks,
> >>
> >> All rejoice. This has been finally implemented.
> >>
> >> Cheers
> >>
> >> On 7 Feb 2018 08:33, "Andre" <an...@fucs.org> wrote:
> >>
> >>> 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 <ottobackwards@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-lists@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 <js...@apache.org>
> >> wrote:
> >>>>
> >>>>> Should we file an infra ticket on this?
> >>>>>
> >>>>> 19.01.2018, 13:56, "Zeolla@GMail.com" <ze...@gmail.com>:
> >>>>>> I would give that +1 as well.
> >>>>>>
> >>>>>> Jon
> >>>>>>
> >>>>>> On Fri, Jan 19, 2018 at 3:32 PM Casey Stella <ce...@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>>> I could get behind that.
> >>>>>>>
> >>>>>>> On Fri, Jan 19, 2018 at 3:31 PM, Andre <an...@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?issues@nifi.apache.org
> >>>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>>
> >>>>>> Jon
> >>>>>
> >>>>> -------------------
> >>>>> Thank you,
> >>>>>
> >>>>> James Sirota
> >>>>> PMC- Apache Metron
> >>>>> jsirota AT apache DOT org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>
>
>
Re: [DISCUSS] Time to remove github updates from dev?
Posted by Simon Elliston Ball <si...@simonellistonball.com>.
I would say we should also update our website with subscription information.
Simon
> On 4 Apr 2018, at 18:51, Nick Allen <ni...@nickallen.org> wrote:
>
> https://lists.apache.org/list.html?issues@metron.apache.org
>
> On Tue, Mar 20, 2018 at 5:06 PM, Otto Fowler <ot...@gmail.com>
> wrote:
>
>> How about a link?
>>
>>
>>
>> On March 19, 2018 at 08:16:46, Andre (andre-lists@fucs.org) wrote:
>>
>> Folks,
>>
>> All rejoice. This has been finally implemented.
>>
>> Cheers
>>
>> On 7 Feb 2018 08:33, "Andre" <an...@fucs.org> wrote:
>>
>>> 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 <ot...@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-lists@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 <js...@apache.org>
>> wrote:
>>>>
>>>>> Should we file an infra ticket on this?
>>>>>
>>>>> 19.01.2018, 13:56, "Zeolla@GMail.com" <ze...@gmail.com>:
>>>>>> I would give that +1 as well.
>>>>>>
>>>>>> Jon
>>>>>>
>>>>>> On Fri, Jan 19, 2018 at 3:32 PM Casey Stella <ce...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>>> I could get behind that.
>>>>>>>
>>>>>>> On Fri, Jan 19, 2018 at 3:31 PM, Andre <an...@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?issues@nifi.apache.org
>>>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Jon
>>>>>
>>>>> -------------------
>>>>> Thank you,
>>>>>
>>>>> James Sirota
>>>>> PMC- Apache Metron
>>>>> jsirota AT apache DOT org
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
Re: [DISCUSS] Time to remove github updates from dev?
Posted by Nick Allen <ni...@nickallen.org>.
https://lists.apache.org/list.html?issues@metron.apache.org
On Tue, Mar 20, 2018 at 5:06 PM, Otto Fowler <ot...@gmail.com>
wrote:
> How about a link?
>
>
>
> On March 19, 2018 at 08:16:46, Andre (andre-lists@fucs.org) wrote:
>
> Folks,
>
> All rejoice. This has been finally implemented.
>
> Cheers
>
> On 7 Feb 2018 08:33, "Andre" <an...@fucs.org> wrote:
>
> > 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 <ot...@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-lists@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 <js...@apache.org>
> wrote:
> >>
> >> > Should we file an infra ticket on this?
> >> >
> >> > 19.01.2018, 13:56, "Zeolla@GMail.com" <ze...@gmail.com>:
> >> > > I would give that +1 as well.
> >> > >
> >> > > Jon
> >> > >
> >> > > On Fri, Jan 19, 2018 at 3:32 PM Casey Stella <ce...@gmail.com>
> >> wrote:
> >> > >
> >> > >> I could get behind that.
> >> > >>
> >> > >> On Fri, Jan 19, 2018 at 3:31 PM, Andre <an...@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?issues@nifi.apache.org
> >> > >> >
> >> > >
> >> > > --
> >> > >
> >> > > Jon
> >> >
> >> > -------------------
> >> > Thank you,
> >> >
> >> > James Sirota
> >> > PMC- Apache Metron
> >> > jsirota AT apache DOT org
> >> >
> >> >
> >>
> >>
> >
>
Re: [DISCUSS] Time to remove github updates from dev?
Posted by Otto Fowler <ot...@gmail.com>.
How about a link?
On March 19, 2018 at 08:16:46, Andre (andre-lists@fucs.org) wrote:
Folks,
All rejoice. This has been finally implemented.
Cheers
On 7 Feb 2018 08:33, "Andre" <an...@fucs.org> wrote:
> 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 <ot...@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-lists@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 <js...@apache.org> wrote:
>>
>> > Should we file an infra ticket on this?
>> >
>> > 19.01.2018, 13:56, "Zeolla@GMail.com" <ze...@gmail.com>:
>> > > I would give that +1 as well.
>> > >
>> > > Jon
>> > >
>> > > On Fri, Jan 19, 2018 at 3:32 PM Casey Stella <ce...@gmail.com>
>> wrote:
>> > >
>> > >> I could get behind that.
>> > >>
>> > >> On Fri, Jan 19, 2018 at 3:31 PM, Andre <an...@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?issues@nifi.apache.org
>> > >> >
>> > >
>> > > --
>> > >
>> > > Jon
>> >
>> > -------------------
>> > Thank you,
>> >
>> > James Sirota
>> > PMC- Apache Metron
>> > jsirota AT apache DOT org
>> >
>> >
>>
>>
>