Transfer is a bit more complicated compared to just importing the master branch, but here is an example where it was done: https://issues.apache.org/jira/browse/INFRA-17168
If you go that route, you would then push back the asf-site branch after the external repo was moved (and replaced the current repo). Regarding the issues, you could start using JIRA for new issues (update the contributor instructions) and just let the github issues dry up. JIRA has an API. I used that few years ago for import for another project. It was a bit of work, but if anyone is interested to research that I can probably dig up the scripts. On Mon, Feb 25, 2019 at 9:53 AM Vinoth Chandar < [email protected]> wrote: > Moving Greg to bcc, since we are unblocked. > > On Mon, Feb 25, 2019 at 9:34 AM [email protected] <[email protected]> > wrote: > > > > > > > - What does everyone think about using Github transfer to move project > > over? To me, it seems clean (stars, watches all would probably move as > > well). I can approach Uber's admin if we feel the same > > +1 > > - Shall we migrate manually to JIRA? (127 issues, it's not a lot of work > > per se). Is there strong interest to stick to Github Issues? > > > > +1 . I feel moving all the issues together would be better as any new > > folks who plan to contribute can look at one place for known tickets. > > On Monday, February 25, 2019, 7:20:55 AM PST, Vinoth Chandar < > > [email protected]> wrote: > > > > Hello all, > > > > Chris wrote back and the gist is > > > > - Its not clear if there is a clean GH issues => Jira migrator > > - We could move the current incubator-hudi to incubator-hudi-site > > - Transfer uber/hudi repo to apache/incubator-hudi > > - Issues and Code will move over seamlessly > > > > Later we can decide if we want to use JIRA or Github issues. > > > > Couple questions for the list > > > > - What does everyone think about using Github transfer to move project > > over? To me, it seems clean (stars, watches all would probably move as > > well). I can approach Uber's admin if we feel the same > > - Shall we migrate manually to JIRA? (127 issues, it's not a lot of work > > per se). Is there strong interest to stick to Github Issues? > > > > Thanks > > Vinoth > > > > On Sun, Feb 24, 2019 at 7:13 AM Vinoth Chandar <[email protected]> > wrote: > > > > > Hello greg, > > > > > > For context, this is the jira > > > https://issues.apache.org/jira/browse/INFRA-17870 > > > > > > Thanks > > > Vinoth > > > > > > On Sun, Feb 24, 2019 at 6:44 AM Suneel Marthi <[email protected]> > > wrote: > > > > > >> On Sun, Feb 24, 2019 at 9:26 AM Vinoth Chandar <[email protected]> > > wrote: > > >> > > >> > @thomas, not a must. But there are a lot of valid issues there. We > > will > > >> > anyway move most of them over manually if automation is not > possible. > > >> > > > >> > Per earlier conversation, I think the hudi PPMC preferred jira since > > its > > >> > easier to cross link to other > > >> > asf projects. > > >> > > > >> > On drawing attention to the ticket, would pinging the task again on > > >> > asfinfra be a gentler next step? > > >> > > > >> > > >> I would do that, as a mentor on Hudi - cc'ing Greg Stein here to > kindly > > >> look into this. > > >> > > >> > > > >> > On Sat, Feb 23, 2019 at 9:15 AM Thomas Weise <[email protected]> > wrote: > > >> > > > >> > > You could also consider leaving the old github issues where they > are > > >> and > > >> > > start fresh with JIRA. There is no mandate to migrate old issues. > > >> > > > > >> > > > > >> > > On Sat, Feb 23, 2019 at 9:10 AM Luciano Resende < > > [email protected] > > >> > > > >> > > wrote: > > >> > > > > >> > > > Based on your integration question, let me ask in a different > way, > > >> is > > >> > > > it a must to start using JIRA? Maybe the question on [email protected] > > >> > > > should be, is it ok to continue using github issues? > > >> > > > > > >> > > > On Sat, Feb 23, 2019 at 8:27 AM Vinoth Chandar < > [email protected] > > > > > >> > > wrote: > > >> > > > > > > >> > > > > Update: Still blocked on response from infra on the tool. > > >> > > > > > > >> > > > > Although looks like, a GitHub transfer would have worked > great. > > >> Not > > >> > > sure > > >> > > > > about how well it would have integrated into ASF repository & > > JIRA > > >> > etc > > >> > > > > though. > > >> > > > > > > >> > > > > On Mon, Feb 18, 2019 at 3:10 PM Vinoth Chandar < > > [email protected] > > >> > > > >> > > > wrote: > > >> > > > > > > >> > > > > > Thanks for the suggestion, Luciano! > > >> > > > > > https://issues.apache.org/jira/browse/INFRA-17870 > > >> > > > > > > > >> > > > > > On Sat, Feb 16, 2019 at 11:32 AM Luciano Resende < > > >> > > [email protected] > > >> > > > > > > >> > > > > > wrote: > > >> > > > > > > > >> > > > > >> Please check with infra (e.g. create a issue) as I believe > > they > > >> > > have a > > >> > > > > >> tool > > >> > > > > >> for that. > > >> > > > > >> > > >> > > > > >> On Fri, Feb 15, 2019 at 19:51 Vinoth Chandar < > > >> [email protected]> > > >> > > > wrote: > > >> > > > > >> > > >> > > > > >> > Hello all, > > >> > > > > >> > > > >> > > > > >> > How about moving off issues to JIRA and updating docs > > >> > accordingly? > > >> > > > This > > >> > > > > >> > would then leave us with simply code move remaining. > > >> > > > > >> > > > >> > > > > >> > Few questions/request-for-advice > > >> > > > > >> > > > >> > > > > >> > - Is there a good tool for GitHub issues => JIRA > > >> > migration?(there > > >> > > > is a > > >> > > > > >> > JIRA importer plugin, but don't think its installed on > ASF > > >> Jira) > > >> > > > > >> > - Once issues are moved over (manually or otherwise), I > am > > >> > > thinking > > >> > > > > >> about > > >> > > > > >> > disabling issues on GitHub. This will help us divert > > >> community > > >> > > > towards > > >> > > > > >> > JIRA. Ok? > > >> > > > > >> > > > >> > > > > >> > > > >> > > > > >> > Thanks > > >> > > > > >> > Vinoth > > >> > > > > >> > > > >> > > > > >> -- > > >> > > > > >> Sent from my Mobile device > > >> > > > > >> > > >> > > > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > -- > > >> > > > Luciano Resende > > >> > > > http://twitter.com/lresende1975 > > >> > > > http://lresende.blogspot.com/ > > >> > > > > > >> > > > > >> > > > >> > > > > > >
