Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Ernesto Posse <eposse@cs.queensu.ca>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: "Stéphane Glondu" <steph@glondu.net>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Licenses - Confusion
Date: Thu, 23 May 2013 17:39:19 -0400	[thread overview]
Message-ID: <CABY2naxpfe9GVC-j9hVEs5s5DWiHFvjz1Tj8eXXema9g9xmUXA@mail.gmail.com> (raw)
In-Reply-To: <C6FD1926B72D449E8139A262070D7D33@erratique.ch>

[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]

On Thu, May 23, 2013 at 4:41 AM, Daniel Bünzli
<daniel.buenzli@erratique.ch>wrote:

> Le jeudi, 23 mai 2013 à 07:36, Stéphane Glondu a écrit :
> > I would say BSD-style licenses cater for the needs of organizations, and
> > GPL-style ones cater for individuals.
>
>
> Well as everyone seems to know and speak for the others, here's my take.
>
> Regardless of copyleft -- which I'm certain could be expressed in a
> BSD-like concise way -- I would personally say that BSD-style licenses are
> for humans and GPL-style for lawyers.
>
> If you need a lawyer to understand your freedom you are not free anymore.
> Stop feeding the lawyers and the bureaucrats.
>
>
I'm afraid this is a little bit too naive. I am not a lawyer, and I agree
that the GPL is quite unreadable, but the choice of licence does matter,
and has real consequences. A BSD or MIT licence is very permissive, but one
could argue that they is too permissive, with no attribution required for
example. If what you want is "anyone can use it in any way and I don't
care", then BSD-like is fine. GPL, imposes restrictions on derivative
works, which could be argued as limiting freedom. My point is, not all
"copyleft" licences are the same, and the choice depends on your needs and
how you want people to use your software. Personally I like Apache. I find
it much more readable than GPL and without the same derivative works
restrictions.




> Best,
>
> Daniel
>
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>



-- 
Ernesto Posse

Modelling and Analysis in Software Engineering
School of Computing
Queen's University - Kingston, Ontario, Canada

[-- Attachment #2: Type: text/html, Size: 2754 bytes --]

  parent reply	other threads:[~2013-05-23 21:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 12:34 oliver
2013-05-22 12:39 ` Anil Madhavapeddy
2013-05-22 16:40   ` Marek Kubica
2013-05-22 13:02 ` Török Edwin
2013-05-22 17:19   ` Adrien Nader
2013-05-23  6:36     ` Stéphane Glondu
2013-05-23  8:41       ` Daniel Bünzli
2013-05-23 21:07         ` Marek Kubica
2013-05-23 21:36         ` Stéphane Glondu
2013-05-23 22:28           ` Daniel Bünzli
2013-05-23 21:39         ` Ernesto Posse [this message]
2013-05-23 21:45         ` Chet Murthy
2013-05-23 22:11         ` Stefano Zacchiroli
2013-05-23 22:52   ` oliver

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABY2naxpfe9GVC-j9hVEs5s5DWiHFvjz1Tj8eXXema9g9xmUXA@mail.gmail.com \
    --to=eposse@cs.queensu.ca \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    --cc=steph@glondu.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox