I most of the time go for the BSD license. It's flexible and open.
http://www.opensource.org/osi3.0/licenses/bsd-license.php
- Sylvain
Russ,
I usually use the BSD license, too.
Don Demsak
Microsoft MVP (XML)
.NET Solutions Consultant
blog: www.donxml.com
Every major protocol that's taken off has had a bsd style license or less
restrictive for at least 1 of it's earliest primary implementations. SMTP had
sendmail (BSD like), NNTP had inn (BSD like), DNS had BIND (BSD like), HTTP
had the original cern originated httpd which was made public domain.
As a result, based on a history of success rather than anything else I'm a
strong advocate of the BSD license for anything protocol related :-)
Michael.
BSD is a fine choice, but I did want to be sure folks know of AFL 3.0,
which is my usual pick of licenses these days:
http://www.opensource.org/licenses/afl-3.0.php
I like its legal clarity (it was written by Lawrence Rosen himself), but
the practical terms pretty much correspond with BSD.
--
Uche Ogbuji http://uche.ogbuji.net
Linked-in profile: http://www.linkedin.com/in/ucheogbuji
Articles: http://uche.ogbuji.net/tech/publications/
Definitely clear on its legal terms indeed. I will keep it in mind.
- Sylvain
Given the fact that this is really a BSD license that simply provides
greater detail and clarity, I'm inclined to suggest this as at very
least something we should consider as our primary focus.
Thoughts?