OK
my personal pick is
http://sourceforge.net/projects/phpaga/
it is BSD, can be converted to GPL, is PHP, and is well used.
and probably better if the developper is confident with the used api.
Ok, so the C code would be the best? something small and fast.
Maybe some gdgraph stuff.
Maybe faster but you have to take care this can be integrated in php
pages for access management
The other thing that i would like to know from you,
what is your statement on webservices and plugins,
can I make non-free plugins and atttach them to gforge? If so
what interfaces allow that? GForge is GPL, and this brings us back to
the question of the linking.
gforge code is GPL, just have to follow GPL rules for all what you do
See this thread on debian legal :
http://lists.debian.org/debian-legal/1999/debian-legal-199907/msg00113.html
"> What you're saying is that you may not use GPL'd software in
conjunction
with non GPL software, from a user's standpoint. That's completely
absurd
in my opinion. The user may not link GPL'd software with non GPL'd
software at his own discretion?
No, I'm saying that you may not distribute GPL'd software in conjuction
with software with license which conflicts with the GPL. This is not a
problem from the users standpoint, this is a problem from a
distributors
standpoint. It means that for example Debian can't distribute php
linked
against a GPL library. "
Anyway, I am just learning about the PHP licensing, but i do have my
wonders.
mike