You see, even with something as simple as trying to indicate "widely available and recognised free software licencing agreements"--Ie. What I was trying to indicate when I used "GPL licences"--you need a lawyer to verify what you are saying.

The FSF has found cause to make distinctions regarding the following 28 free software licence agreements (from FSF):

  1. GNU GPL.
  2. GNU LGPL
  3. Licence of Guile
  4. License of the run-time units of the GNU Ada compiler
  5. X11 licence
  6. Expat Licence
  7. Standard ML of New Jersey Copyright License
  8. Public Domain
  9. Cryptix General License
  10. Modified BSD license
  11. License of ZLib
  12. License of the iMatix Standard Function Library
  13. W3C Software Notice and License
  14. Berkeley Database License (aka the Sleepycat Software Product License)
  15. OpenLDAP License, Version 2.7
  16. License of Python 1.6a2 and earlier versions
  17. License of Python 2.0.1, 2.1.1, and newer versions
  18. License of Perl
  19. Clarified Artistic License
  20. Zope Public License version 2.0
  21. Intel Open Source License (as published by OSI)
  22. License of Netscape Javascript
  23. eCos license version 2.0
  24. Eiffel Forum License, version 2
  25. License of Vim, Version 6.1 or later
  26. Boost Software License
  27. EU DataGrid Software License
  28. The license of Ruby

And those are just the "GPL compatible" ones! There is another list of 30+ "incompatible" ones, and 20 or so more including the original "Artistic licence", that are not considered "free software licences" at all.

Me, I'm just a layman. I ain't about to argue with the FSF.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^16: Why non-core CPAN modules can't be used in large corporate environments. by BrowserUk
in thread Why non-core CPAN modules can't be used in large corporate environments. by Moron

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.