> > Nope, it isn't. After initially switching to GPL V3+ we have decided > to remain at GPL V2+ for now. Since we have discussed this quite > extensively in the past here is no need to rehash this here. I don't > need another drawn out licensing discussion. >
Well, I don't see why it is a concern since giac can be relicensed to version 2. > > I do so that I can fix bug myself using gdb. Sometimes > > in the future, I'll certainly have to make some documentation for > > programmers, but I'll move it as a priority only if I'm sure active > > developers are using giac. > > This is certainly a chicken/egg problem. I did revisit risch.[cc|h] > and vecteur.[cc|h] and rish.cc was better commented than I did > remember. But what I am missing is doxygen style documentation of > input and output parameters. > This is the developer doc I plan to write someday, but it is currently not a main priority. > > Yes, we agree here, too, but we are only interested in factorization > here at the moment. Otherwise everything else seems to be covered by > other components in Sage. > I believed that you would appreciate to see other developers focus on the aspects you do not want to develop themselves, like integration which BTW is far more than just implementing the Risch algorithm. If you don't see any interest on integrating giac in sage, fine, as I said earlier I do not *need* sage, of course I would appreciate feedback from their users, but I can continue my way expanding giac and integrating the same libraries into giac (as sage does) and certainly I will not loose anymore time justifying me here when I read the ton of some of your next comments, like: > We are interested in only a small part of the functionality > and giac has been looked at in the past [that discuss has happened > face to face at Sage Days or in IRC] and we never came to the > conclusion that it was worth the effort [i.e. the cost was not worth > the effort]: > >giac has potential problems [please correct me if I am wrong]: > > * a low busfactor, i.e. few if not one active developer > * no really visible developer community > * no public CVS or version control system Integration into sage would certainly help! > * unsatisfying documentation The focus in on xcas user documentation > * unkown build issues: of course, since they are unknown. Note however that it is ported to mac os and win and arm linux and wince. > * unknown memory leak issues [Did you ever run valgrind? If not I > would highly recommend it] yes > * unknown portability issues: Sun Forte, MSVC, alignment problems, > endianess issues, see arm port. I never cared about sun or msvc. > * small test suite: it seems that there are only the files in $GIAC/ > check to do some testing. It is only a handful of files compared to > 52,000 doctests in Sage. You would be surprised by the number of bugs that are caught by definite integration. Giac is certainly not bugfree but it can be and begins to be used as an alternative to maple. >I am sure all of the issues > above can be overcame [in case they do exist], but I am not going to > work on any of this unless factorization becomes more important than > the ports. And I don't see that happening because certain institutions > are paying me to port to Solaris and Windows. And if one pays for the > band that person decides what music is played. > > So: What should you do? Start with an optional or experimental spkg > and prove me wrong. ;) > That is not the way I see collaboration. I will not do all the work myself. >If > factorization could be broken out from giac in a reasonably small > package (like factory in Singular) we might have something to discuss, > but as a whole I do not see this as a good fit. > Obviously factorization depends on all the basic algorithms like gcd, polynomials etc. and it can not be isolated easily. And if it's the only thing you would be interested in giac, then there is indeed no need to continue this discussion :-) --~--~---------~--~----~------------~-------~--~----~ 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://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
