Github as their own open archive program
(https://archiveprogram.github.com/) and works together with known software
/ archive websites. In particular, the code itself is archived via the
EU-funded Software Heritage foundation and issue/PR metadata for all public
repos are in GHTorrent / GHArchive. Thus, in the unlikely situation of
massive policy changes of GH including a complete removal/block of their
API, the data is still there and the community will probably develop
migration tools to whatever platform will become popular then.
In addition, one can download a "migration archive" from github which
should include all data
(https://docs.github.com/en/enterprise-server@3.6/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom#generating-a-migration-archive)
or use one of the third-party solutions that keep backups per repo
(https://github.com/marketplace?category=backup-utilities&query=sort%3Apopularity-desc&type=&verification=).
On Friday, 30 September 2022 at 10:21:15 UTC+2 dim...@gmail.com wrote:
> On Fri, Sep 30, 2022 at 8:59 AM Marc Mezzarobba
> wrote:
> >
> > John H Palmieri wrote:
> > > You would think that this would be a solved problem: others in the
> > > open source community must have be in the practice of backing up their
> > > GitHub info.
> >
> > The following tools seem fairly complete:
> >
> > - https://github-backup.branchable.com/ (but I'm getting timeouts with
> > it),
> >
> > - https://github.com/josegonzalez/python-github-backup (not tested).
> >
> > IMO we should at the very least have something like that running before
> > making the switch. We should also refrain from using features of github
> > not supported by our backup tool.
>
> While migrating to github, we can get json records for each issue we
> created to replace tickets.
> (they are complete records, everything may be recreated from them)
>
> Then we can set up a GitHub actions to produce such jsons for
> created/updated issues and PRs,
> see e.g.
> https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#issue_comment
>
> I think this is more robust than running tools which make global copies.
> (These updated jsons need to be be stored somewhere)
>
> Dima
>
>
>
> >
> > --
> > Marc
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "sage-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to sage-devel+...@googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/th67k9%246eq%241%40ciao.gmane.io
> .
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/6553f91a-5d75-498e-9e60-ef3577364ae8n%40googlegroups.com.
