Any tips for Maxima migrating to GitHub

[Oscar Benjamin]

Hi all,

There have been some discussions and tentative attempts to migrate
Maxima from SourceForge to GitHub e.g.:
https://sourceforge.net/p/maxima/mailman/message/58794267/

I'm wondering how Sage managed to migrate issues from trac to GitHub
while still preserving things like who is the author of a comment or
the timestamp of the comment etc. I don't see how in GitHub's API you
can set those things.

For example this issue was migrated:
https://github.com/sagemath/sage/issues/33458

Somehow it shows my GitHub account opening the issue along with the
GitHub handles for other people who commented and the timestamps are I
assume those that were pulled from trac. I can't see how to make that
happen with Github migration scripts that I have seen or from the REST
API docs.

If anyone has any tips for a good way to do this then I am sure that
the Maxima developers would appreciate it.

--
Oscar

[David Roe]

The code that we used for the Trac to github migration is in this repository.  Some things (including associating trac usernames with github usernames and creating issues, PRs and comments made by those users) required cooperation with Github and did not just use the public API.  I was not involved in that aspect of the migration, so I'll let others speak to exactly what was involved.

David

--
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/CAHVvXxSs4gKgD_dPTkyNm6CiM7exMdoLBaA26m1G9N2f3%2BipxA%40mail.gmail.com.

[Oscar Benjamin]

Okay, so the public API can't do this. That explains why I couldn't
see how to do it.

I'll pass this on.

Thanks David and Dima.

On Thu, 11 Jul 2024 at 20:32, Dima Pasechnik <dim...@gmail.com> wrote:
>
> The migration has to be performed by GitHub staff (or at least it was
> the case 1.5 years ago).
> You'll want to get in touch with https://github.com/abbycabs who's
> leading these sort tasks at GitHub.
>
> So you'd need to write an exporter (that's the repo David links), and
> debug it, before handing over to them, on a (trial) instance of GitHub
> Enterprise server (you can install it for free and use for a month or
> so - you'd need a Linux server to run it on).
>
> HTH,
> Dima

[Dima Pasechnik]

The migration has to be performed by GitHub staff (or at least it was
the case 1.5 years ago).
You'll want to get in touch with https://github.com/abbycabs who's
leading these sort tasks at GitHub.

So you'd need to write an exporter (that's the repo David links), and
debug it, before handing over to them, on a (trial) instance of GitHub
Enterprise server (you can install it for free and use for a month or
so - you'd need a Linux server to run it on).

HTH,
Dima




On Thu, Jul 11, 2024 at 5:50 PM Oscar Benjamin
<oscar.j....@gmail.com> wrote:
>