On Mon, Jul 28, 2008 at 7:27 PM, Elliott Slaughter <elliottslaughter@gmail.com> wrote:
Also, I'm wondering what licensing requirements common-lisp.net puts on projects its hosts. If I create a repository with my account, will that be public to the internet? If it is, then I assume I need some sort of license (even if I don't think my project is far enough along that anyone else would want to contribute)... so what would you recommend?
Since I happen know you work for Franz as well, could you tell me if there are any additional licensing constraints when working on a project which happens to only run on ACL? That is, the current iteration of my project uses AllegroCache and thus can't run on any other Lisp system. Does this influence what licenses I can use with my project?
Huh, it seems licence requirements have vanished from the clnet website -- or maybe they never ended up there in the first place, not sure. At any rate, Common-Lisp.net has since it's inception been open to all open source / free software projects building on Common Lisp. No implemention specific restrictions. That said, clnet is for *public* code. If you use clnet to store your personal code without releasing it into the open, that's not in the spirit of the service provided. My *biased* recommendation is the MIT licence <http://www.opensource.org/licenses/mit-license.php>, but whatever suits *your* needs is fine: in the absence of a public notice on the clnet site, assume that any license which fulfills DFSG <http://www.debian.org/social_contract#guidelines> is fine. Cheers, -- Nikodemus, not a clnet admin anymore, but I still think I know this stuff well enough