To move this forward…..
From my reading/investigation, the only “change” that would be required post migration would be for everyone to update the URL’s for their repos in their clones. (Change git-wip.apache.org -> gitbox.apache.org). That’s it. So the short term impact would be minimal. What we would gain includes: 1) writable GitHub repo - instead of pushing to apache, you COULD push to GitHub. Not a big deal for anyone though. Most of us just do “git push” and where it goes doesn’t really matter. 2) However, (1) allows using the “merge” button on the pull requests. For simple pull requests, this can be easier. 3) This also allows use of the “Close” button on the pull requests for requests that won’t be merged. No more “bogus/empty” commits to close a PR 4) It also would allow assigning reviewers and labels and such the PR’s. We’ve never really used those (since they aren’t usable right now), but they could be useful in the future. Anyway, would anyone object if I filed a ticket to migrate? I don’t see any major downsides as it’s just a URL change. Do you think we need a formal vote or is a lazy-consensus ok? That said, even if we agree to file the ticket, it doesn’t mean INFRA will approve it. Dan > On Jul 29, 2017, at 3:01 AM, Dennis Kieselhorst <[email protected]> wrote: > > I already replied yesterday, somehow Ponymail seems not to deliver > anything at the moment, so I try again... > >> We'd obviously all have to update the URL's for our local repos, is > that it? > > Basically yes, I don't see any disadvantages. > > See this thread for experiences in Accumulo project: > https://lists.apache.org/thread.html/3b50ac9e449b3f0621478bba9ee1ad01340800982b0e7af17ecff792@%3Cdev.accumulo.apache.org%3E > > We should continue using JIRA and not switch to GitHub issues. > > Regards > Dennis -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
