Re: Æsthetic Permissive License - For Approval

[Russ Nelson]

Sean B. Palmer writes:
 > I've looked at the five shortest OSI-approved licenses:

Looking at other licenses and copying them is a REALLY BAD practice.
What if they're all really crappy licenses relative to current
practice?

Write the license you want to write.

 > Do you recommend me to publish the version containing "Entities may
 > use, copy, sell" as the text requested to be approved by the OSI and
 > FSF instead of the current submission text? How will it increase my
 > chances specifically of the OSI Board approving it?

Do not "teach to the test".  Write the license that accomplishes the
goal you have in mind.  Better for you to have a license that makes
you happy rather than one that makes us happy and yet gets you no
users.

Software licensing is not an end in itself.  You write a license to
get users.  Worry about THAT and OSD compliance later.  (We happen to
believe that they coincide very closely, but we may be wrong.)

-- 
--my blog is at    http://blog.russnelson.com   | Software that needs
Crynwr sells support for free software  | PGPok | documentation is software
521 Pleasant Valley Rd. | +1 315-323-1241       | that needs repair.
Potsdam, NY 13676-3213  |     Sheepdog          |