[sage-devel] Behavior of optional packages

I am not sure if the subject reflects exactly what I mean but I have just seen a change of behavior. It is maybe intended but I do not see it reflected in the documentation or I did not know how to look for it. I use quite often the optional package sirocco. It was installed in my develop branch

Re: [sage-devel] Any tips for Maxima migrating to GitHub

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

Re: [sage-devel] Any tips for Maxima migrating to GitHub

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 wrote: > > The migration has to be performed by GitHub staff (or at least it was > the case 1.5 years ago). > You'll want

Re: [sage-devel] Any tips for Maxima migrating to GitHub

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

[sage-devel] Any tips for Maxima migrating to GitHub

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 o