> > indefinitely for a new SageNB release *IS* a big problem. So as a > minimal > > proposal, how about we just take over the SageNB github repo and make > > releases whenever we need them. Which really isn't all that often. > > +1 -- I agree 100% with everything above. If anybody wants added to > the repo, let me know. > > Thanks to all for the action on this. I only took over the sagenb repo management reluctantly, because no one else who still cared was willing to do it. I do think there is still some valuable work on it - particularly by J. Miguel Farto (see https://github.com/migeruhito/sagenb/commits/mynb still under active development Mar 9) and Jonathan Gutow on proxy issues. But those people perhaps were not as close to the "core" project and so I took responsibility for sagenb itself. But I am happy for anyone else who wants to sign off their name on merges to take responsibility (as well as for breakages!), as I have been completely overwhelmed with work and realistically cannot do more than I've been doing with micro-releases of pull requests, which I do try to test rather diligently.
-- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
