>> Obviously I want to minimize the work I need to do, while doing enough >> changes, so that the result will not be Sage as requested by Michael. >> :) > > I think the above is fine. In fact, I think it would be cool if you > go one step further > and make this a full standalone project "Source Python Distribution", > with its own website, mailing list, bug tracker, etc. This > definitely solves a problem, hence is likely to have a community grow > up around it. That would lead to lots of useful feedback back and > forth between Sage and SPD.
Ok, I think this is what is needed and what many people would appreciate. Yes, I wanted to create a standalone project just for one of my projects, e.g. like Sage does for the packages that are in Sage, but yesterday I came to the conclusion that it makes much more sense to just create a full python source distribution. I hope to start it this weekend. We'll see how it goes. The scripts will be GPL (and thus the whole thing will be GPL), but I hope it will not be a showstopper for people from the scipy community -- and if there is sufficient interest, someone can write new scripts that supports the Sage interface, that could be BSD and then the whole thing could be BSD. I myself don't care, for me this is just a distribution, like Debian, which is mostly GPL as well. Ondrej --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
