+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) <
[email protected]> 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 <[email protected]>
> 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 <[email protected]>
> > 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 <[email protected]> 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
> >>>
> >>
>
>

Reply via email to