Re: Need help with GitHub Issues migration

> On 24. Feb 2025, at 16:56, David Niklas via mc-devel <mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org> wrote:
> 
> On Mon, 24 Feb 2025 08:18:50 +0100
> "Yury V. Zaytsev" <[email protected]> wrote:
>>> On 24. Feb 2025, at 01:20, David Niklas via mc-devel
>>> <mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org> wrote:
>>> 
>>> I know it's probably a bit late for this, but maybe you should
>>> consider that tying yourself/project to github isn't the best idea in
>>> the world.  
>> 
>> So what is the best idea in the world?
> 
> If only I knew!
> 
> There's gitlab and sourceforge, amoung others, I'm sure. For bug reports
> some projects use bugzilla. The linux kernel still does bug reports and
> fixes through the ML.
> 
> What's insufficient about the current system?

I tried to explain this and what I think about other options I have considered so far in the opening email.

> I'm more worried about what becomes of the code bases and devs than
> perturbed for any other reason.

As for the code base, I maintain an active mirror at repo.or.cz:

https://repo.or.cz/midnight-commander.git

Regarding issues and other data, there seems to be a migration API:

https://docs.github.com/en/migrations/using-ghe-migrator/exporting-migration-data-from-githubcom#generating-a-migration-archive

I guess we'd have to script something on an OSU OSL VM to pull a regular backup there.

> Sorry it's so long. I hope it helps. Thanks for the work you've done on
> MC over the years.

Not sure if it helped, but your words of appreciation are very much valued, thank you.



-- 
mc-devel mailing list
mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org
https://lists.midnight-commander.org/mailman/listinfo/mc-devel