[sage-devel] Re: DISCUSS: move Sage development to Github
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 suppose the "right" way to refer to ML posts would be by Message-Id, but nobody does that, and many people apparently do not understand such references or have no convenient tools to follow them... (I once had someone complain when I used a Message-Id to refer to sage-devel on trac.) -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/thefq9%2413t8%241%40ciao.gmane.io.
[sage-devel] Re: DISCUSS: move Sage development to Github
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 > information. In fact, they are sometimes referred to on trac, via > super-opaque URLs. So I suspect google groups going down (which is probably > a less unlikely event than github ending) would actually damage those links > irretrievably. > I guess they are "backed up" by other news aggregators? Sometimes those are the hits that come up first in Google search, ironically. E.g. https://www.mail-archive.com/sage-devel@googlegroups.com/msg105313.html Which also points out that we already rely on proprietary software for something fairly vital ... not judging that either way, but it's worth mentioning. -- 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/06028961-8a39-458b-9093-08b8aa8654e9n%40googlegroups.com.
[sage-devel] Re: DISCUSS: move Sage development to Github
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 URLs. So I suspect google groups going down (which is probably a less unlikely event than github ending) would actually damage those links irretrievably. I recognize that we have limited resources for backing up stuff. We should be using our resources and time in a smart way to back up things that will have most effect. But it's probably worth it for someone to spend a bit of to determine how to back up sage-devel (that's easy going forward since it can just send email digests; and someone may have been storing those already) and how to refer to threads -- perhaps a date is better than a URL -- as long as we can have a list archive that allows searching by date (I'm not so sure google's web interface allows it), and then perhaps draw the conclusion that it's not worth the effort to archive? -- 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/ef44f7bf-5b78-43c2-897f-694cad213861n%40googlegroups.com.
[sage-devel] Re: DISCUSS: move Sage development to Github
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 > 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.com/sagemath/cypari2 > - https://github.com/sagemath/sagetex > - https://github.com/sagemath/pplpy > - https://github.com/sagemath/cysignals > - https://github.com/sagemath/memory_allocator > > > > > > On Friday, September 30, 2022 at 12:59:15 AM UTC-7 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. >> >> -- >> 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/ec2262fd-fe9c-4d8a-8698-9aad517bf108n%40googlegroups.com.
[sage-devel] Re: DISCUSS: move Sage development to Github
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.com/sagemath/cypari2 - https://github.com/sagemath/sagetex - https://github.com/sagemath/pplpy - https://github.com/sagemath/cysignals - https://github.com/sagemath/memory_allocator On Friday, September 30, 2022 at 12:59:15 AM UTC-7 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. > > -- > 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/1589bc2f-08ca-46f8-889a-6ed16dd18cacn%40googlegroups.com.
Re: [sage-devel] Re: DISCUSS: move Sage development to 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 / 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=sort%3Apopularity-desc==). 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.
Re: [sage-devel] Re: DISCUSS: move Sage development to Github
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+unsubscr...@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/CAAWYfq1qC8%3DnOmW84TgPR6AvNMu-EN8DXAXkBSk8t%3DzOegVLZA%40mail.gmail.com.
[sage-devel] Re: DISCUSS: move Sage development to Github
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. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/th67k9%246eq%241%40ciao.gmane.io.
