It looks like the GitHub Danger Zone can transfer a repository? It's not clear if it can go from Personal -> Organization though. I see Personal -> Personal and Organization -> Organization.
https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository Mike McCandless http://blog.mikemccandless.com On Sun, Jun 26, 2022 at 6:40 PM Tomoko Uchida <tomoko.uchida.1...@gmail.com> wrote: > > > > >> >> 2022年6月27日(月) 5:16 Michael Sokolov <msoko...@gmail.com>: >> >>> as for this access control/script monitoring problem, I wonder whether >>> we could import all the issues into a new github repo owned by >>> whomever is running the script, and then transfer from there to the >>> lucene repo? It would be an extra step involving another script (or >>> something), but maybe(?) that one could be much simpler since it is >>> github->github?? If this works out, we could have full control of the >>> first step and only hand off to infra the simpler copying job. >>> >>> >> I don't see the API or tool that transfers all issues from one repo to >> another repo. >> > > To be exact, I don't see the API or tool that transfers all issues from > one repo to another repo while keeping cross-issue links. > If we want to preserve cross-issue links, there's no difference between > "Jira to GitHub" and "GitHub to GitHub". > > >> >>> On Sat, Jun 25, 2022 at 7:53 AM Tomoko Uchida >>> <tomoko.uchida.1...@gmail.com> wrote: >>> > >>> > I may have to share another practical consideration on the migration >>> that I haven't mentioned yet. >>> > >>> > We are not allowed to have admin access to the lucene GitHub repo, so >>> can't run the import job(s) on ourselves. >>> > We'll have to make a tool with clear instructions for the migration >>> and pass it to infra team, then support them via the jira (or slack?) if >>> there are any problems. >>> > See https://issues.apache.org/jira/browse/INFRA-20118 >>> > >>> > We can do some preparation locally (e.g. dump Jira issues and convert >>> them to importable format to GitHub), but the actual first and second pass >>> import will be done by infra team. >>> > I think I myself won't be able to have close contact with the infra >>> team if the migration operation is too complicated due to the time >>> difference and my communication ability - I'm not good at real-time >>> conversation in English. >>> > So if we need a complex migration plan, I think I'll have to find >>> someone who is willing to take over the job. >>> > >>> > >>> > >>> > 2022年6月25日(土) 19:19 Tomoko Uchida <tomoko.uchida.1...@gmail.com>: >>> >> >>> >> Hi Dawid, >>> >> >>> >> > Emm.. sorry for being slow - what is it that you want me to do? :) >>> Unwatch->Ignore? >>> >> >>> >> I'm sorry for being ambiguous. Could you set your notification >>> setting on the repository as "Participating and @mentions"? >>> >> In the testing of migration scripts, I will import many fake issues >>> where your account is linked as the original reporter/author with real >>> mentions, like this example. >>> >> https://github.com/mocobeta/migration-test-1/issues/111 >>> >> If they do not disturb your inbox with spam notifications then the >>> test is successful. >>> >> >>> >> With regard to attachments: >>> >> >>> >> > 1) create a (separate?) git repository or branch with a separate >>> root in the lucene repository with all jira attachments upon importing them. >>> >> > 2) there are about 7k issues with attachments in Jira. We can split >>> them into 25-issue batches and ask the crowd to port them manually >>> >> >>> >> Thanks for your suggestion, I don't come up with other options >>> either. Both would need others' permission and/or extra work, so I think we >>> can't control the process and outcome. >>> >> For 1), we'll need to ask infra to create a repository and run >>> another long-running batch, and it'll complicate the migration instructions >>> - we'll not be allowed to have access tokens to commit files to an ASF repo >>> from a program. >>> >> For 2), I'm not sure how many people want to volunteer for the manual >>> work. >>> >> >>> >> I cannot promise it will be eventually done, then I would leave it as >>> a limitation of the migration. >>> >> If there are no controllable solutions (to me) on this, I may ask >>> others if we should migrate existing issues to GitHub "even if we can't >>> migrate any attachments and have to keep them in Jira forever". Let me keep >>> myself neutral about the idea of migrating all Jira issues, sorry... I'm >>> working on this not to push it but to provide information and gain a >>> certain agreement. >>> >> >>> >> Tomoko >>> >> >>> >> >>> >> 2022年6月25日(土) 16:12 Dawid Weiss <dawid.we...@gmail.com>: >>> >>> >>> >>> >>> >>> Hi Tomoko, >>> >>> >>> >>>> >>> >>>> There are two ways to receive notifications as you know, 1) watch >>> all activities and 2) receive notifications only when you are mentioned >>> (default). >>> >>>> I excluded your github account from marking up with backticks `` to >>> create hyperlinks. Could you unwatch the repo again and then observe your >>> inbox for a while, so that we can also test 2)? >>> >>>> >>> https://github.com/mocobeta/sandbox-lucene-10557/blob/main/migration/src/jira2github_import.py#L21 >>> >>> >>> >>> >>> >>> Emm.. sorry for being slow - what is it that you want me to do? :) >>> Unwatch->Ignore? >>> >>> >>> >>>> >>> >>>> In this Spring issue, the "attachment" link points to the original >>> Jira file - so they still use Jira as a file server. >>> >>> >>> >>> >>> >>> Ahh... right. In that case I have two ideas: >>> >>> >>> >>> 1) create a (separate?) git repository or branch with a separate >>> root in the lucene repository with all jira attachments upon importing >>> them. This could be structured in subfolders, for example: >>> >>> >>> >>> jira/xyz/attachment-1.jpg >>> >>> >>> >>> if this repository is checked in to github, the links to attachment >>> could point at the "raw" git-serving service github offers. I'm not sure it >>> emits proper content-types (for images, etc). Alternatively, it could be >>> github-docs, which does serve them properly for static content. >>> >>> >>> >>> It will not support searches, of course, but it will be a consistent >>> copy. >>> >>> >>> >>> 2) there are about 7k issues with attachments in Jira. We can split >>> them into 25-issue batches and ask the crowd to port them manually... It >>> will take time but once the issues are ported, it can be done incrementally >>> over a longer time stretch, no rush there. >>> >>> >>> >>> Dawid >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >>> For additional commands, e-mail: dev-h...@lucene.apache.org >>> >>>
