Hi,
please set up a project for me called CL+SSL (note: plus, not minus ;-)).
Thanks, David
Hi,
David Lichteblau david@lichteblau.com writes:
please set up a project for me called CL+SSL (note: plus, not minus ;-)).
Ok! :-)
What's the license?
Regards, Mario.
Hi,
Quoting Mario S. Mommer (mmommer@common-lisp.net):
David Lichteblau david@lichteblau.com writes:
please set up a project for me called CL+SSL
What's the license?
it's a fork of Eric Marsden's SSL-CMUCL, which comes under LGPL, so that will be the license initially.
(However, CL-SSL, which is a fork of the same code based, is apparently distributed under Lisp-LGPL. So I will probably ask Eric about whether he approved that license change and would allow it for CL+SSL, too. If he happens to relax the license even further I wouldn't be opposed to a BSD license either.)
But for now LGPL, since I haven't contacted Eric yet.
Thanks, David
Hi,
Bad news from the project name front. Unix can't have a cl+ssl group name, and our projects are managed in such a way that we need each project name to be a group name.
As this isn't particularily enlightened, I could now stop with this madness and allow project names and groupnames to differ (as they do already wrt case). Within bounds, of course. So your project can call itself cl+ssl, but the groupname would be, unless you sugest something else, cl-plus-ssl. That would be in you directory, email lists, etc.
Unless, of course, you would prefer to change the name of the project. People would tend to use the email handle anyway, and you will bump into that little unix problem in all sorts of places, so perhaps this is a better idea.
As soon as you decide on this, I open your project.
Reagards, Mario.
Hi,
Quoting Mario S. Mommer (mmommer@common-lisp.net):
Bad news from the project name front. Unix can't have a cl+ssl group name, and our projects are managed in such a way that we need each project name to be a group name.
OK...
Calling the group and project "cl-plus-ssl" will be fine, I think.
(In the end this project will end up having multiple loosely related CVS modules (cl+ssl, trivial-https, and probably trivial-gray-streams), the latter two of which are too trivial to deserve their own projects, so I will probably just list them as "subprojects" on the same webpage. That way confusion between the different project name and cvs module name will be minimal anyway.)
Thanks, David