Nathann: > I can't help but notice that you say "we" when you say what should be done, and you say "you" when there is actual work ahead. Will you help? Or will you wait for Sage developers to do it?
It occurred to me that another reason I've been doing this is because it gives me a sense for what I *have* to do versus what other people will do. There's no point in me doing something if I suggest it,and other people are more than competent and willing to do it. As an example, I've suggested numerous times that we should massively refactor the sage library to be a bunch of smaller Python libraries, develop them say on github (?), use Pypi and pip. If people would realize how important it is that we revamp how Sage development is done in a much less monolithic way, and better using existing tools, then I would be happy and enjoy watching as people do the revamp (e.g., like happened with switching from Mercurial to Git, which I didn't do much on, but definitely supported). As it is, I sadly see that nobody seems to "get it" regarding how broken our development process is right now. So, I figure I'll have to do something. Unfortunately, I can't do anything now, due to lack of time. I hope that either I'm totally wrong, or that I do have time before Sage gets into deeper trouble. William On Tue, Jan 26, 2016 at 10:05 AM, Henri Girard <henri.gir...@gmail.com> wrote: > Wouldn't be possible to make a cliquer package ? Cliquer has already been a standard Sage package since at least 2009. > > > > Le 26/01/2016 18:20, William Stein a écrit : >> >> On Tue, Jan 26, 2016 at 9:02 AM, Nathann Cohen <nathann.co...@gmail.com> >> wrote: >>>> >>>> contributions. E.g., they won't even consider a new component be >>>> added to Python unless somebody clearly commits to supporting the >>>> contribution for "five years". And of course the people making that >>>> commitment have to be reputable. We should do the same for Sage -- >>> >>> >>> <sarcasm> >>> Don't you think we should start by doing the same for Sage's own source >>> code? Anybody who proposes a patch should agree to do the >>> debugging/maintenance of what (s)he added for the next 5 years? Looks >>> weird >>> to only have this high level of expectation for third-party code only, >>> and >>> not for our own. >>> </sarcasm> >> >> Hey I was just reporting on a conversation with Guido about what they >> *already* do with Python. >> >>> In Sage, we are at a level where some files don't have a clear "regular >>> maintainer". We would need to be 10x more developpers to enforce such >>> rules. >>> >> Indeed -- Python probably has 10x more developers... maybe someday we >> will have way more developer time too. We don't now, as we are >> massively under-resourced. >> >>> For 'cliquer' in particular, maybe we could propose upstream a >>> autotoolized >>> build system, and see how it goes? We did it for 'planarity' not so long >>> ago >>> (and perhaps with others?). Our spkg-install file indeed contains several >>> platform-specific instructions. >> >> Huge +1. I'm all for Sage devs contributing upstream :-) >> >>> Nathann >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "sage-support" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to sage-support+unsubscr...@googlegroups.com. >>> To post to this group, send email to sage-support@googlegroups.com. >>> Visit this group at https://groups.google.com/group/sage-support. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> > > -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-support+unsubscr...@googlegroups.com. > To post to this group, send email to sage-support@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
