On Fri, Apr 15, 2016 at 10:08 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2016-04-15 22:06, John H Palmieri wrote: >> >> I don't know if there are any right now, but I think that many of the >> recent changes in sagenb have come because there were changes in the >> Sage library. Maybe "difficult" is not the right word, but this adds an >> artificial layer of complexity: instead of making a few possibly trivial >> changes in the relevant sagenb files within Sage, for example when the >> location of the built documentation moved, it takes a pull request, >> someone to handle that request, someone to put together a new sagenb >> release, etc. It often (almost always?) ends up being the same people >> working on the Sage trac ticket and the sagenb pull request, so we're >> adding some inefficiencies to the system. If we could deal with the >> issues with just a trac ticket, that would be better. > > > +1, this is an excellent summary of the problem.
Okay,but that's totally not unusual in software development. I work in about a dozen different repositories on a given day and it doesn't make a difference. Clearly we just need more help on maintaining sagenb. I need to check with Nicolas if this is within the purview of ODK (I'm not sure that it is given that part of ODK seems to be aimed toward moving away from sagenb). But it's clear that sagenb still needs to be maintained. Shoving it back into sage is a backwards move though, and in the long term only makes the task of packaging and distributing sage more difficult. To me it feels like self-sabotage. Best, Erik -- 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.
