You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficcontrol.apache.org by "Eric Friedrich (efriedri)" <ef...@cisco.com> on 2017/08/28 16:38:13 UTC
[VOTE] Bugtracking in Github Issues
We currently use JIRA Issues to track all of the Traffic Control bugs.
Now that we have write access to Github, we can move back to GH Issues for bug tracking.
This will be a better workflow because its one fewer tool and account to have to interact with. This will hopefully lower the bar for new contributors to file bugs and engage with the product. We can also help use it (along with the milestones) to create more useful changelogs and release notes.
A possible downside is that the Issues are maybe less flexible than JIRA in terms of permissions, workflow, fields, etc. However, we were using Issues before we entered the incubator and that was fine for us. Hopefully no one has developed an attachment for JIRA in the last year.
Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll assume a lazy consensus if there aren’t enough votes.
—Eric
Re: [VOTE] Bugtracking in Github Issues
Posted by Robert Butts <ro...@gmail.com>.
+1
> 1. Github * Has very little in the way of organizational options
I view Github's simplicity as a plus. Jira has a steep learning curve, and
is discouraging to potential new committers. Every separate tool we have
(issues, wiki, docs) are more obstacles to new people. Github's built-ins
are exponentially easier for new people to start contributing with.
On Mon, Aug 28, 2017 at 12:44 PM, Durfey, Ryan <Ry...@comcast.com>
wrote:
> I am -1 on this, but count take it with grain of salt since I am not
> developing code. I am generally system agnostic, but the maturity of Jira
> makes it a far superior tool for tracking, reporting, and staying
> organized. I would argue that since this is an open source project
> organization is significantly more important since a lot of disparate users
> need to be able to understand what is going on at a high level.
>
>
> 1. Github
> * Has very little in the way of organizational options
> * Offers issues, labels, a basic Kanban and epics which are immature
> 2. Jira
> * Has very mature set of organization and reporting tools and
> integrates with many other platforms
> * Offers components, releases, labels, and epics which are all
> mature
> * Offers custom searches which can be shared across the project
> * Offers customizable kanbans by release, component, with swimlanes
> that can also be customized
> * Offers customizable workflow so you can have intake and backlog
> statuses added
> * Offers customizable report templates
>
>
>
> Ryan Durfey M | 303-524-5099
> CDN Support (24x7): 866-405-2993 or cdn_support@comcast.com<mailto:
> cdn_support@comcast.com>
>
>
> From: Dan Kirkwood <da...@gmail.com>
> Reply-To: "dev@trafficcontrol.incubator.apache.org" <
> dev@trafficcontrol.incubator.apache.org>
> Date: Monday, August 28, 2017 at 10:50 AM
> To: "dev@trafficcontrol.incubator.apache.org" <
> dev@trafficcontrol.incubator.apache.org>
> Subject: Re: [VOTE] Bugtracking in Github Issues
>
> +1
>
> On Mon, Aug 28, 2017 at 10:38 AM, Eric Friedrich (efriedri)
> <ef...@cisco.com>> wrote:
> We currently use JIRA Issues to track all of the Traffic Control bugs.
>
> Now that we have write access to Github, we can move back to GH Issues for
> bug tracking.
>
> This will be a better workflow because its one fewer tool and account to
> have to interact with. This will hopefully lower the bar for new
> contributors to file bugs and engage with the product. We can also help use
> it (along with the milestones) to create more useful changelogs and release
> notes.
>
> A possible downside is that the Issues are maybe less flexible than JIRA
> in terms of permissions, workflow, fields, etc. However, we were using
> Issues before we entered the incubator and that was fine for us. Hopefully
> no one has developed an attachment for JIRA in the last year.
>
>
> Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll assume
> a lazy consensus if there aren’t enough votes.
>
> —Eric
>
>
>
>
>
Re: [VOTE] Bugtracking in Github Issues
Posted by "Durfey, Ryan" <Ry...@comcast.com>.
I am -1 on this, but count take it with grain of salt since I am not developing code. I am generally system agnostic, but the maturity of Jira makes it a far superior tool for tracking, reporting, and staying organized. I would argue that since this is an open source project organization is significantly more important since a lot of disparate users need to be able to understand what is going on at a high level.
1. Github
* Has very little in the way of organizational options
* Offers issues, labels, a basic Kanban and epics which are immature
2. Jira
* Has very mature set of organization and reporting tools and integrates with many other platforms
* Offers components, releases, labels, and epics which are all mature
* Offers custom searches which can be shared across the project
* Offers customizable kanbans by release, component, with swimlanes that can also be customized
* Offers customizable workflow so you can have intake and backlog statuses added
* Offers customizable report templates
Ryan Durfey M | 303-524-5099
CDN Support (24x7): 866-405-2993 or cdn_support@comcast.com<ma...@comcast.com>
From: Dan Kirkwood <da...@gmail.com>
Reply-To: "dev@trafficcontrol.incubator.apache.org" <de...@trafficcontrol.incubator.apache.org>
Date: Monday, August 28, 2017 at 10:50 AM
To: "dev@trafficcontrol.incubator.apache.org" <de...@trafficcontrol.incubator.apache.org>
Subject: Re: [VOTE] Bugtracking in Github Issues
+1
On Mon, Aug 28, 2017 at 10:38 AM, Eric Friedrich (efriedri)
<ef...@cisco.com>> wrote:
We currently use JIRA Issues to track all of the Traffic Control bugs.
Now that we have write access to Github, we can move back to GH Issues for bug tracking.
This will be a better workflow because its one fewer tool and account to have to interact with. This will hopefully lower the bar for new contributors to file bugs and engage with the product. We can also help use it (along with the milestones) to create more useful changelogs and release notes.
A possible downside is that the Issues are maybe less flexible than JIRA in terms of permissions, workflow, fields, etc. However, we were using Issues before we entered the incubator and that was fine for us. Hopefully no one has developed an attachment for JIRA in the last year.
Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll assume a lazy consensus if there aren’t enough votes.
—Eric
Re: [VOTE] Bugtracking in Github Issues
Posted by Steve Malenfant <sm...@gmail.com>.
+1
On Mon, Aug 28, 2017 at 1:02 PM, Dewayne Richardson <de...@gmail.com>
wrote:
> +1
>
> On Mon, Aug 28, 2017 at 10:44 AM, Dave Neuman <ne...@apache.org> wrote:
>
> > I thought we already had a vote on this? Maybe I am thinking of the
> "move
> > to github" vote which I assumed to be all-encompassing.
> > Anyway, +1
> >
> > On Mon, Aug 28, 2017 at 10:43 AM, Dan Kirkwood <da...@gmail.com>
> wrote:
> >
> > > +1
> > >
> > > On Mon, Aug 28, 2017 at 10:38 AM, Eric Friedrich (efriedri)
> > > <ef...@cisco.com> wrote:
> > > > We currently use JIRA Issues to track all of the Traffic Control
> bugs.
> > > >
> > > > Now that we have write access to Github, we can move back to GH
> Issues
> > > for bug tracking.
> > > >
> > > > This will be a better workflow because its one fewer tool and account
> > to
> > > have to interact with. This will hopefully lower the bar for new
> > > contributors to file bugs and engage with the product. We can also help
> > use
> > > it (along with the milestones) to create more useful changelogs and
> > release
> > > notes.
> > > >
> > > > A possible downside is that the Issues are maybe less flexible than
> > JIRA
> > > in terms of permissions, workflow, fields, etc. However, we were using
> > > Issues before we entered the incubator and that was fine for us.
> > Hopefully
> > > no one has developed an attachment for JIRA in the last year.
> > > >
> > > >
> > > > Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll
> > > assume a lazy consensus if there aren’t enough votes.
> > > >
> > > > —Eric
> > > >
> > > >
> > >
> >
>
Re: [VOTE] Bugtracking in Github Issues
Posted by Dewayne Richardson <de...@gmail.com>.
+1
On Mon, Aug 28, 2017 at 10:44 AM, Dave Neuman <ne...@apache.org> wrote:
> I thought we already had a vote on this? Maybe I am thinking of the "move
> to github" vote which I assumed to be all-encompassing.
> Anyway, +1
>
> On Mon, Aug 28, 2017 at 10:43 AM, Dan Kirkwood <da...@gmail.com> wrote:
>
> > +1
> >
> > On Mon, Aug 28, 2017 at 10:38 AM, Eric Friedrich (efriedri)
> > <ef...@cisco.com> wrote:
> > > We currently use JIRA Issues to track all of the Traffic Control bugs.
> > >
> > > Now that we have write access to Github, we can move back to GH Issues
> > for bug tracking.
> > >
> > > This will be a better workflow because its one fewer tool and account
> to
> > have to interact with. This will hopefully lower the bar for new
> > contributors to file bugs and engage with the product. We can also help
> use
> > it (along with the milestones) to create more useful changelogs and
> release
> > notes.
> > >
> > > A possible downside is that the Issues are maybe less flexible than
> JIRA
> > in terms of permissions, workflow, fields, etc. However, we were using
> > Issues before we entered the incubator and that was fine for us.
> Hopefully
> > no one has developed an attachment for JIRA in the last year.
> > >
> > >
> > > Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll
> > assume a lazy consensus if there aren’t enough votes.
> > >
> > > —Eric
> > >
> > >
> >
>
Re: [VOTE] Bugtracking in Github Issues
Posted by Dave Neuman <ne...@apache.org>.
I thought we already had a vote on this? Maybe I am thinking of the "move
to github" vote which I assumed to be all-encompassing.
Anyway, +1
On Mon, Aug 28, 2017 at 10:43 AM, Dan Kirkwood <da...@gmail.com> wrote:
> +1
>
> On Mon, Aug 28, 2017 at 10:38 AM, Eric Friedrich (efriedri)
> <ef...@cisco.com> wrote:
> > We currently use JIRA Issues to track all of the Traffic Control bugs.
> >
> > Now that we have write access to Github, we can move back to GH Issues
> for bug tracking.
> >
> > This will be a better workflow because its one fewer tool and account to
> have to interact with. This will hopefully lower the bar for new
> contributors to file bugs and engage with the product. We can also help use
> it (along with the milestones) to create more useful changelogs and release
> notes.
> >
> > A possible downside is that the Issues are maybe less flexible than JIRA
> in terms of permissions, workflow, fields, etc. However, we were using
> Issues before we entered the incubator and that was fine for us. Hopefully
> no one has developed an attachment for JIRA in the last year.
> >
> >
> > Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll
> assume a lazy consensus if there aren’t enough votes.
> >
> > —Eric
> >
> >
>
Re: [VOTE] Bugtracking in Github Issues
Posted by Dan Kirkwood <da...@gmail.com>.
+1
On Mon, Aug 28, 2017 at 10:38 AM, Eric Friedrich (efriedri)
<ef...@cisco.com> wrote:
> We currently use JIRA Issues to track all of the Traffic Control bugs.
>
> Now that we have write access to Github, we can move back to GH Issues for bug tracking.
>
> This will be a better workflow because its one fewer tool and account to have to interact with. This will hopefully lower the bar for new contributors to file bugs and engage with the product. We can also help use it (along with the milestones) to create more useful changelogs and release notes.
>
> A possible downside is that the Issues are maybe less flexible than JIRA in terms of permissions, workflow, fields, etc. However, we were using Issues before we entered the incubator and that was fine for us. Hopefully no one has developed an attachment for JIRA in the last year.
>
>
> Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll assume a lazy consensus if there aren’t enough votes.
>
> —Eric
>
>
Re: [VOTE] Bugtracking in Github Issues
Posted by Jason Tucker <ja...@gmail.com>.
+1
On Mon, Aug 28, 2017 at 4:43 PM, Jan van Doorn <jv...@knutsel.com> wrote:
> +1
>
> On Mon, Aug 28, 2017 at 10:38 AM Eric Friedrich (efriedri) <
> efriedri@cisco.com> wrote:
>
> > We currently use JIRA Issues to track all of the Traffic Control bugs.
> >
> > Now that we have write access to Github, we can move back to GH Issues
> for
> > bug tracking.
> >
> > This will be a better workflow because its one fewer tool and account to
> > have to interact with. This will hopefully lower the bar for new
> > contributors to file bugs and engage with the product. We can also help
> use
> > it (along with the milestones) to create more useful changelogs and
> release
> > notes.
> >
> > A possible downside is that the Issues are maybe less flexible than JIRA
> > in terms of permissions, workflow, fields, etc. However, we were using
> > Issues before we entered the incubator and that was fine for us.
> Hopefully
> > no one has developed an attachment for JIRA in the last year.
> >
> >
> > Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll
> assume
> > a lazy consensus if there aren’t enough votes.
> >
> > —Eric
> >
> >
> >
>
Re: [VOTE] Bugtracking in Github Issues
Posted by Jan van Doorn <jv...@knutsel.com>.
+1
On Mon, Aug 28, 2017 at 10:38 AM Eric Friedrich (efriedri) <
efriedri@cisco.com> wrote:
> We currently use JIRA Issues to track all of the Traffic Control bugs.
>
> Now that we have write access to Github, we can move back to GH Issues for
> bug tracking.
>
> This will be a better workflow because its one fewer tool and account to
> have to interact with. This will hopefully lower the bar for new
> contributors to file bugs and engage with the product. We can also help use
> it (along with the milestones) to create more useful changelogs and release
> notes.
>
> A possible downside is that the Issues are maybe less flexible than JIRA
> in terms of permissions, workflow, fields, etc. However, we were using
> Issues before we entered the incubator and that was fine for us. Hopefully
> no one has developed an attachment for JIRA in the last year.
>
>
> Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll assume
> a lazy consensus if there aren’t enough votes.
>
> —Eric
>
>
>
Re: [VOTE] Bugtracking in Github Issues
Posted by Leif Hedstrom <zw...@apache.org>.
> On Aug 29, 2017, at 4:47 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
>
>> On Aug 28, 2017, at 10:38 AM, Eric Friedrich (efriedri) <ef...@cisco.com> wrote:
>>
>> We currently use JIRA Issues to track all of the Traffic Control bugs.
>>
>> Now that we have write access to Github, we can move back to GH Issues for bug tracking.
>>
>> This will be a better workflow because its one fewer tool and account to have to interact with. This will hopefully lower the bar for new contributors to file bugs and engage with the product. We can also help use it (along with the milestones) to create more useful changelogs and release notes.
>>
>> A possible downside is that the Issues are maybe less flexible than JIRA in terms of permissions, workflow, fields, etc. However, we were using Issues before we entered the incubator and that was fine for us. Hopefully no one has developed an attachment for JIRA in the last year.
>>
>>
>> Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll assume a lazy consensus if there aren’t enough votes.
>
>
>
> I’m +1 on this, but did you verify with the Incubator powers that this is allowed? Another option is to defer this until you are down with incubation, and make the migration to a TLP include moving more of your workflow over to Github proper.
I also should point out that Github Issues is vastly inferior to Jira, in every aspect other than that more people know and are used to the shitty Github system :-).
Cheers,
— Leif
Re: [VOTE] Bugtracking in Github Issues
Posted by Jeremy Mitchell <mi...@gmail.com>.
+1 but the fact that only committers can be assigned to issues is a big
problem in my opinion.
On Tue, Aug 29, 2017 at 7:16 PM, Eric Friedrich (efriedri) <
efriedri@cisco.com> wrote:
> Thanks Leif-
> I’ll check with the Incubator gurus. We already pulled the trigger, so
> at this point its more about asking for forgiveness.
>
> —Eric
> On Aug 29, 2017, at 6:47 PM, Leif Hedstrom <zwoop@apache.org<mailto:zwoop
> @apache.org>> wrote:
>
>
> On Aug 28, 2017, at 10:38 AM, Eric Friedrich (efriedri) <
> efriedri@cisco.com<ma...@cisco.com>> wrote:
>
> We currently use JIRA Issues to track all of the Traffic Control bugs.
>
> Now that we have write access to Github, we can move back to GH Issues for
> bug tracking.
>
> This will be a better workflow because its one fewer tool and account to
> have to interact with. This will hopefully lower the bar for new
> contributors to file bugs and engage with the product. We can also help use
> it (along with the milestones) to create more useful changelogs and release
> notes.
>
> A possible downside is that the Issues are maybe less flexible than JIRA
> in terms of permissions, workflow, fields, etc. However, we were using
> Issues before we entered the incubator and that was fine for us. Hopefully
> no one has developed an attachment for JIRA in the last year.
>
>
> Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll assume
> a lazy consensus if there aren’t enough votes.
>
>
>
> I’m +1 on this, but did you verify with the Incubator powers that this is
> allowed? Another option is to defer this until you are down with
> incubation, and make the migration to a TLP include moving more of your
> workflow over to Github proper.
>
> — Leif
>
>
Re: [VOTE] Bugtracking in Github Issues
Posted by "Eric Friedrich (efriedri)" <ef...@cisco.com>.
Thanks Leif-
I’ll check with the Incubator gurus. We already pulled the trigger, so at this point its more about asking for forgiveness.
—Eric
On Aug 29, 2017, at 6:47 PM, Leif Hedstrom <zw...@apache.org>> wrote:
On Aug 28, 2017, at 10:38 AM, Eric Friedrich (efriedri) <ef...@cisco.com>> wrote:
We currently use JIRA Issues to track all of the Traffic Control bugs.
Now that we have write access to Github, we can move back to GH Issues for bug tracking.
This will be a better workflow because its one fewer tool and account to have to interact with. This will hopefully lower the bar for new contributors to file bugs and engage with the product. We can also help use it (along with the milestones) to create more useful changelogs and release notes.
A possible downside is that the Issues are maybe less flexible than JIRA in terms of permissions, workflow, fields, etc. However, we were using Issues before we entered the incubator and that was fine for us. Hopefully no one has developed an attachment for JIRA in the last year.
Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll assume a lazy consensus if there aren’t enough votes.
I’m +1 on this, but did you verify with the Incubator powers that this is allowed? Another option is to defer this until you are down with incubation, and make the migration to a TLP include moving more of your workflow over to Github proper.
— Leif
Re: [VOTE] Bugtracking in Github Issues
Posted by Leif Hedstrom <zw...@apache.org>.
> On Aug 28, 2017, at 10:38 AM, Eric Friedrich (efriedri) <ef...@cisco.com> wrote:
>
> We currently use JIRA Issues to track all of the Traffic Control bugs.
>
> Now that we have write access to Github, we can move back to GH Issues for bug tracking.
>
> This will be a better workflow because its one fewer tool and account to have to interact with. This will hopefully lower the bar for new contributors to file bugs and engage with the product. We can also help use it (along with the milestones) to create more useful changelogs and release notes.
>
> A possible downside is that the Issues are maybe less flexible than JIRA in terms of permissions, workflow, fields, etc. However, we were using Issues before we entered the incubator and that was fine for us. Hopefully no one has developed an attachment for JIRA in the last year.
>
>
> Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll assume a lazy consensus if there aren’t enough votes.
I’m +1 on this, but did you verify with the Incubator powers that this is allowed? Another option is to defer this until you are down with incubation, and make the migration to a TLP include moving more of your workflow over to Github proper.
— Leif