On 24 April 2015 at 10:32, than...@debian.org <than...@debian.org> wrote: > Whether it is an embedded fork in sage or it gets its own git repo on the > sage github account.. Someone from the sage community would have to fix bugs > in both cases.
Yes! But I think that David Harvey *is* a member of the Sage community (unless he says otherwise...) John > > Am Freitag, 24. April 2015 10:37:56 UTC+2 schrieb John Cremona: >> >> Who is the author of hyperellfrob? >> >> There is a point in addition to Michael's: maintaining a fork which >> only differs with respect to libtools packaging is one thing, but we >> would also need someone to take responsibility for any bugs found in >> the code, if the original author was not able, willing or available to >> respond. >> >> John >> >> On 24 April 2015 at 00:54, Michael Orlitzky <mic...@orlitzky.com> wrote: >> > On 04/23/2015 04:56 PM, Jeroen Demeyer wrote: >> >>> >> >>> Can't we work with upstream (the authors) to package these? >> >> For starters, none of these seem very active projects. In particular, >> >> hyperellfrob and bernmm have their last release in 2008 and 2009. >> >> >> >> Second, what if the authors don't care? >> >> >> > >> > There are two kinds of don't care: >> > >> > 1. The author doesn't like autotools or doesn't want to accept >> > outside contributions. >> > >> > 2. The code was for an old project and the author can't be bothered >> > with it any more. >> > >> > Both have the same solution: fork it and make releases on the sagemath >> > github or wherever. In the case of (2), this is obviously best for >> > everyone. If it's (1) instead, then most of our additions will be >> > independent of the "real" code making it trivial for us to merge >> > upstream changes. Then our fork will be the better fork (since it builds >> > easily and has all the same features), and people will use our fork >> > instead. Eventually the author will come around, or if not, that's not a >> > huge problem either. >> > >> > We're essentially maintaining a fork now, so it wouldn't necessarily be >> > more work after we're done auto-tooling it. >> > >> > -- >> > 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 post to this group, send email to sage-...@googlegroups.com. >> > Visit this group at http://groups.google.com/group/sage-devel. >> > For more options, visit https://groups.google.com/d/optout. > > -- > 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 http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
