Nils Bruin wrote:
> Speaking of backups ... do we backup the sage-devel, sage-support news
> groups?
They are on gmane, and presumably some sage developers have more or less
complete archives on their own computers...
> In fact, they are sometimes referred to on trac, via
> super-opaque URLs.
I
On Sunday, October 2, 2022 at 2:16:00 PM UTC-4 Nils Bruin wrote:
> Speaking of backups ... do we backup the sage-devel, sage-support news
> groups? It contains a lot of stuff that loses relevance with time, but
> every now and again there are discussions that contain important bits of
> infor
Speaking of backups ... do we backup the sage-devel, sage-support news
groups? It contains a lot of stuff that loses relevance with time, but
every now and again there are discussions that contain important bits of
information. In fact, they are sometimes referred to on trac, via
super-opaque U
I've opened https://trac.sagemath.org/ticket/34624 to organize the
discussion on backup and coordinate work on it.
On Saturday, October 1, 2022 at 9:48:51 AM UTC-7 Matthias Koeppe wrote:
> Thanks for the pointers!
> I see that the Cython project uses python-github-backup to back up their
> rep
Thanks for the pointers!
I see that the Cython project uses python-github-backup to back up their
repo to https://github.com/cython/cython-issues
I would propose that we set up such backups for the projects that are
already hosted at https://github.com/sagemath/:
In particular:
- https://github
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 / GHArch
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:
>
> - h
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),