On 9/25/07, Bill Hart <[EMAIL PROTECTED]> wrote: > If SAGE developers weren't so thin on the ground, I'm sure that we > could fork GMP. I'd be interested in doing so, for various reasons. > There's already code in the FLINT project which could go straight into > a forked GMP. I'd also like to get around to providing decent assembly > support for the PS3. > > But I alone do not have the time to maintain such an enormous package, > especially given that I'm already codeveloper of FLINT. A group of us > could manage it, I'm sure. But whether it would be successful, I > couldn't say.
I feel precisely the same way. I also hope Sage developers will become a bit more thick on the ground. That said, it might be good to think about what team would do a GMP fork, if it were to happen, just in case. Probably you, me, Jason Martin, ?? Jason Martin remarked: > Maintaining build scripts for assembly level code for > hundreds of platforms has > got to be a painfully tedious task that no one else > wants to take on. The first thing I would do if I forked GMP would be to greatly reduce the number of supported platforms, in the same way that Ubuntu supports far fewer platforms than Debian. I would chose the same platforms that Sage targets (and that Sage *wants* to target). The second thing I would do is release the forked version (i.e., all _new_ code in the forked version) under GPL (not LGPL) to prevent usage by Maple/Magma of our version. The third thing would be to integrate in all the patches to GMP that we currently distribute that aren't part of the official GMP. The fourth thing would be to choose a new name for the project. The fifth thing would be to setup a website with bug tracker, wiki, mailing lists, and all the other standard tools of an open source project. That sounds like a lot of work. I'm glad I'm not forking GMP. -- William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
