You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficcontrol.apache.org by Dave Neuman <ne...@apache.org> on 2017/05/17 14:51:00 UTC
Moving Traffic Control the "full" github
While at ApaceCon, a few of us attended a talk about navigating the
incubator where we were informed that "full" Github is now available for
podlings. This gives us the ability to use github issues, to use github
wiki, to assign PRs, to add tags to PRs, and the "merge PR" button among
other things. It sounds like the process would take our repo down for a
short period - minutes not hours - but the URL shouldn't change. I know we
just got all of our issues moved to Jira, but we would need to move them
over to github as well.
Since the apache way is to have a discussion before a vote, I thought I
would start the discussion on this topic now and if we feel like this is
worth pursuing, we start a vote. So....thoughts?
Thanks,
Dave
Re: Moving Traffic Control the "full" github
Posted by Dave Neuman <ne...@apache.org>.
This wasn't the vote thread, this was a discuss thread that everyone voted
on. However, I do believe the vote thread is ready to be closed.
On Mon, May 22, 2017 at 12:08 PM, Chris Lemmons <al...@gmail.com> wrote:
> This vote has now been open for the requisite 72 hours with basically
> universal consensus in favour of the move. Dave, I believe your motion
> carries. :)
>
> On Wed, May 17, 2017 at 10:57 AM Hank Beatty <hb...@apache.org> wrote:
>
> > +1
> >
> > On 05/17/2017 10:51 AM, Dave Neuman wrote:
> > > While at ApaceCon, a few of us attended a talk about navigating the
> > > incubator where we were informed that "full" Github is now available
> for
> > > podlings. This gives us the ability to use github issues, to use
> github
> > > wiki, to assign PRs, to add tags to PRs, and the "merge PR" button
> among
> > > other things. It sounds like the process would take our repo down for
> a
> > > short period - minutes not hours - but the URL shouldn't change. I
> know
> > we
> > > just got all of our issues moved to Jira, but we would need to move
> them
> > > over to github as well.
> > >
> > > Since the apache way is to have a discussion before a vote, I thought I
> > > would start the discussion on this topic now and if we feel like this
> is
> > > worth pursuing, we start a vote. So....thoughts?
> > >
> > >
> > > Thanks,
> > > Dave
> > >
> >
>
Re: Moving Traffic Control the "full" github
Posted by Chris Lemmons <al...@gmail.com>.
This vote has now been open for the requisite 72 hours with basically
universal consensus in favour of the move. Dave, I believe your motion
carries. :)
On Wed, May 17, 2017 at 10:57 AM Hank Beatty <hb...@apache.org> wrote:
> +1
>
> On 05/17/2017 10:51 AM, Dave Neuman wrote:
> > While at ApaceCon, a few of us attended a talk about navigating the
> > incubator where we were informed that "full" Github is now available for
> > podlings. This gives us the ability to use github issues, to use github
> > wiki, to assign PRs, to add tags to PRs, and the "merge PR" button among
> > other things. It sounds like the process would take our repo down for a
> > short period - minutes not hours - but the URL shouldn't change. I know
> we
> > just got all of our issues moved to Jira, but we would need to move them
> > over to github as well.
> >
> > Since the apache way is to have a discussion before a vote, I thought I
> > would start the discussion on this topic now and if we feel like this is
> > worth pursuing, we start a vote. So....thoughts?
> >
> >
> > Thanks,
> > Dave
> >
>
Re: Moving Traffic Control the "full" github
Posted by Hank Beatty <hb...@apache.org>.
+1
On 05/17/2017 10:51 AM, Dave Neuman wrote:
> While at ApaceCon, a few of us attended a talk about navigating the
> incubator where we were informed that "full" Github is now available for
> podlings. This gives us the ability to use github issues, to use github
> wiki, to assign PRs, to add tags to PRs, and the "merge PR" button among
> other things. It sounds like the process would take our repo down for a
> short period - minutes not hours - but the URL shouldn't change. I know we
> just got all of our issues moved to Jira, but we would need to move them
> over to github as well.
>
> Since the apache way is to have a discussion before a vote, I thought I
> would start the discussion on this topic now and if we feel like this is
> worth pursuing, we start a vote. So....thoughts?
>
>
> Thanks,
> Dave
>
Re: Moving Traffic Control the "full" github
Posted by "Gelinas, Derek" <De...@comcast.com>.
+1
> On May 17, 2017, at 12:01 PM, Jan van Doorn <jv...@knutsel.com> wrote:
>
> +1
>
>> On Wed, May 17, 2017 at 11:59 AM Dan Kirkwood <da...@gmail.com> wrote:
>>
>> +1 here as well..
>>
>> On Wed, May 17, 2017 at 9:38 AM, Eric Friedrich (efriedri)
>> <ef...@cisco.com> wrote:
>>> I am all for one less tool to use. Also I think it will lower bar to
>> bringing more people into our project if they don’t have to sign up for the
>> ASF JIRA separately.
>>>
>>> —Eric
>>>
>>>> On May 17, 2017, at 10:57 AM, Mark Torluemke <mt...@apache.org>
>> wrote:
>>>>
>>>> Also +1. Part of the move from github.com/Comcast to ASF JIRA included
>> a
>>>> 'scrub', so the move to github.com/apache can likely be scripted.
>>>>
>>>> On Wed, May 17, 2017 at 8:55 AM, Robert Butts <robert.o.butts@gmail.com
>>>
>>>> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> IMO Github issues, wiki, etc are much, much easier to use than
>> Atlassian
>>>>> tools.
>>>>>
>>>>> On Wed, May 17, 2017 at 8:51 AM, Dave Neuman <ne...@apache.org>
>> wrote:
>>>>>
>>>>>> While at ApaceCon, a few of us attended a talk about navigating the
>>>>>> incubator where we were informed that "full" Github is now available
>> for
>>>>>> podlings. This gives us the ability to use github issues, to use
>> github
>>>>>> wiki, to assign PRs, to add tags to PRs, and the "merge PR" button
>> among
>>>>>> other things. It sounds like the process would take our repo down
>> for a
>>>>>> short period - minutes not hours - but the URL shouldn't change. I
>> know
>>>>> we
>>>>>> just got all of our issues moved to Jira, but we would need to move
>> them
>>>>>> over to github as well.
>>>>>>
>>>>>> Since the apache way is to have a discussion before a vote, I thought
>> I
>>>>>> would start the discussion on this topic now and if we feel like this
>> is
>>>>>> worth pursuing, we start a vote. So....thoughts?
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Dave
>>>>>>
>>>>>
>>>
>>
Re: Moving Traffic Control the "full" github
Posted by Jan van Doorn <jv...@knutsel.com>.
+1
On Wed, May 17, 2017 at 11:59 AM Dan Kirkwood <da...@gmail.com> wrote:
> +1 here as well..
>
> On Wed, May 17, 2017 at 9:38 AM, Eric Friedrich (efriedri)
> <ef...@cisco.com> wrote:
> > I am all for one less tool to use. Also I think it will lower bar to
> bringing more people into our project if they don’t have to sign up for the
> ASF JIRA separately.
> >
> > —Eric
> >
> >> On May 17, 2017, at 10:57 AM, Mark Torluemke <mt...@apache.org>
> wrote:
> >>
> >> Also +1. Part of the move from github.com/Comcast to ASF JIRA included
> a
> >> 'scrub', so the move to github.com/apache can likely be scripted.
> >>
> >> On Wed, May 17, 2017 at 8:55 AM, Robert Butts <robert.o.butts@gmail.com
> >
> >> wrote:
> >>
> >>> +1
> >>>
> >>> IMO Github issues, wiki, etc are much, much easier to use than
> Atlassian
> >>> tools.
> >>>
> >>> On Wed, May 17, 2017 at 8:51 AM, Dave Neuman <ne...@apache.org>
> wrote:
> >>>
> >>>> While at ApaceCon, a few of us attended a talk about navigating the
> >>>> incubator where we were informed that "full" Github is now available
> for
> >>>> podlings. This gives us the ability to use github issues, to use
> github
> >>>> wiki, to assign PRs, to add tags to PRs, and the "merge PR" button
> among
> >>>> other things. It sounds like the process would take our repo down
> for a
> >>>> short period - minutes not hours - but the URL shouldn't change. I
> know
> >>> we
> >>>> just got all of our issues moved to Jira, but we would need to move
> them
> >>>> over to github as well.
> >>>>
> >>>> Since the apache way is to have a discussion before a vote, I thought
> I
> >>>> would start the discussion on this topic now and if we feel like this
> is
> >>>> worth pursuing, we start a vote. So....thoughts?
> >>>>
> >>>>
> >>>> Thanks,
> >>>> Dave
> >>>>
> >>>
> >
>
Re: Moving Traffic Control the "full" github
Posted by Dan Kirkwood <da...@gmail.com>.
+1 here as well..
On Wed, May 17, 2017 at 9:38 AM, Eric Friedrich (efriedri)
<ef...@cisco.com> wrote:
> I am all for one less tool to use. Also I think it will lower bar to bringing more people into our project if they don’t have to sign up for the ASF JIRA separately.
>
> —Eric
>
>> On May 17, 2017, at 10:57 AM, Mark Torluemke <mt...@apache.org> wrote:
>>
>> Also +1. Part of the move from github.com/Comcast to ASF JIRA included a
>> 'scrub', so the move to github.com/apache can likely be scripted.
>>
>> On Wed, May 17, 2017 at 8:55 AM, Robert Butts <ro...@gmail.com>
>> wrote:
>>
>>> +1
>>>
>>> IMO Github issues, wiki, etc are much, much easier to use than Atlassian
>>> tools.
>>>
>>> On Wed, May 17, 2017 at 8:51 AM, Dave Neuman <ne...@apache.org> wrote:
>>>
>>>> While at ApaceCon, a few of us attended a talk about navigating the
>>>> incubator where we were informed that "full" Github is now available for
>>>> podlings. This gives us the ability to use github issues, to use github
>>>> wiki, to assign PRs, to add tags to PRs, and the "merge PR" button among
>>>> other things. It sounds like the process would take our repo down for a
>>>> short period - minutes not hours - but the URL shouldn't change. I know
>>> we
>>>> just got all of our issues moved to Jira, but we would need to move them
>>>> over to github as well.
>>>>
>>>> Since the apache way is to have a discussion before a vote, I thought I
>>>> would start the discussion on this topic now and if we feel like this is
>>>> worth pursuing, we start a vote. So....thoughts?
>>>>
>>>>
>>>> Thanks,
>>>> Dave
>>>>
>>>
>
Re: Moving Traffic Control the "full" github
Posted by Chris Lemmons <al...@gmail.com>.
+1. Potential contributors will be much more likely to find issues and
submit fixes with just a GitHub interface and one set of credentials. I
actually prefer Jira to GitHub Issues, but I significantly prefer a single
tool, and GitHub issues will work fine. Plus, the ability to tag PRs and
such will be very helpful. I think that actually gives us integration
options with a CI directly, but maybe not.
On Wed, May 17, 2017 at 9:38 AM Eric Friedrich (efriedri) <
efriedri@cisco.com> wrote:
> I am all for one less tool to use. Also I think it will lower bar to
> bringing more people into our project if they don’t have to sign up for the
> ASF JIRA separately.
>
> —Eric
>
> > On May 17, 2017, at 10:57 AM, Mark Torluemke <mt...@apache.org>
> wrote:
> >
> > Also +1. Part of the move from github.com/Comcast to ASF JIRA included a
> > 'scrub', so the move to github.com/apache can likely be scripted.
> >
> > On Wed, May 17, 2017 at 8:55 AM, Robert Butts <ro...@gmail.com>
> > wrote:
> >
> >> +1
> >>
> >> IMO Github issues, wiki, etc are much, much easier to use than Atlassian
> >> tools.
> >>
> >> On Wed, May 17, 2017 at 8:51 AM, Dave Neuman <ne...@apache.org> wrote:
> >>
> >>> While at ApaceCon, a few of us attended a talk about navigating the
> >>> incubator where we were informed that "full" Github is now available
> for
> >>> podlings. This gives us the ability to use github issues, to use
> github
> >>> wiki, to assign PRs, to add tags to PRs, and the "merge PR" button
> among
> >>> other things. It sounds like the process would take our repo down for
> a
> >>> short period - minutes not hours - but the URL shouldn't change. I
> know
> >> we
> >>> just got all of our issues moved to Jira, but we would need to move
> them
> >>> over to github as well.
> >>>
> >>> Since the apache way is to have a discussion before a vote, I thought I
> >>> would start the discussion on this topic now and if we feel like this
> is
> >>> worth pursuing, we start a vote. So....thoughts?
> >>>
> >>>
> >>> Thanks,
> >>> Dave
> >>>
> >>
>
>
Re: Moving Traffic Control the "full" github
Posted by "Eric Friedrich (efriedri)" <ef...@cisco.com>.
I am all for one less tool to use. Also I think it will lower bar to bringing more people into our project if they don’t have to sign up for the ASF JIRA separately.
—Eric
> On May 17, 2017, at 10:57 AM, Mark Torluemke <mt...@apache.org> wrote:
>
> Also +1. Part of the move from github.com/Comcast to ASF JIRA included a
> 'scrub', so the move to github.com/apache can likely be scripted.
>
> On Wed, May 17, 2017 at 8:55 AM, Robert Butts <ro...@gmail.com>
> wrote:
>
>> +1
>>
>> IMO Github issues, wiki, etc are much, much easier to use than Atlassian
>> tools.
>>
>> On Wed, May 17, 2017 at 8:51 AM, Dave Neuman <ne...@apache.org> wrote:
>>
>>> While at ApaceCon, a few of us attended a talk about navigating the
>>> incubator where we were informed that "full" Github is now available for
>>> podlings. This gives us the ability to use github issues, to use github
>>> wiki, to assign PRs, to add tags to PRs, and the "merge PR" button among
>>> other things. It sounds like the process would take our repo down for a
>>> short period - minutes not hours - but the URL shouldn't change. I know
>> we
>>> just got all of our issues moved to Jira, but we would need to move them
>>> over to github as well.
>>>
>>> Since the apache way is to have a discussion before a vote, I thought I
>>> would start the discussion on this topic now and if we feel like this is
>>> worth pursuing, we start a vote. So....thoughts?
>>>
>>>
>>> Thanks,
>>> Dave
>>>
>>
Re: Moving Traffic Control the "full" github
Posted by Mark Torluemke <mt...@apache.org>.
Also +1. Part of the move from github.com/Comcast to ASF JIRA included a
'scrub', so the move to github.com/apache can likely be scripted.
On Wed, May 17, 2017 at 8:55 AM, Robert Butts <ro...@gmail.com>
wrote:
> +1
>
> IMO Github issues, wiki, etc are much, much easier to use than Atlassian
> tools.
>
> On Wed, May 17, 2017 at 8:51 AM, Dave Neuman <ne...@apache.org> wrote:
>
> > While at ApaceCon, a few of us attended a talk about navigating the
> > incubator where we were informed that "full" Github is now available for
> > podlings. This gives us the ability to use github issues, to use github
> > wiki, to assign PRs, to add tags to PRs, and the "merge PR" button among
> > other things. It sounds like the process would take our repo down for a
> > short period - minutes not hours - but the URL shouldn't change. I know
> we
> > just got all of our issues moved to Jira, but we would need to move them
> > over to github as well.
> >
> > Since the apache way is to have a discussion before a vote, I thought I
> > would start the discussion on this topic now and if we feel like this is
> > worth pursuing, we start a vote. So....thoughts?
> >
> >
> > Thanks,
> > Dave
> >
>
Re: Moving Traffic Control the "full" github
Posted by Robert Butts <ro...@gmail.com>.
+1
IMO Github issues, wiki, etc are much, much easier to use than Atlassian
tools.
On Wed, May 17, 2017 at 8:51 AM, Dave Neuman <ne...@apache.org> wrote:
> While at ApaceCon, a few of us attended a talk about navigating the
> incubator where we were informed that "full" Github is now available for
> podlings. This gives us the ability to use github issues, to use github
> wiki, to assign PRs, to add tags to PRs, and the "merge PR" button among
> other things. It sounds like the process would take our repo down for a
> short period - minutes not hours - but the URL shouldn't change. I know we
> just got all of our issues moved to Jira, but we would need to move them
> over to github as well.
>
> Since the apache way is to have a discussion before a vote, I thought I
> would start the discussion on this topic now and if we feel like this is
> worth pursuing, we start a vote. So....thoughts?
>
>
> Thanks,
> Dave
>