From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 6A4287F7B4 for ; Mon, 10 Feb 2014 15:21:17 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of agarwal1975@gmail.com) identity=pra; client-ip=209.85.216.177; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="agarwal1975@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of agarwal1975@gmail.com designates 209.85.216.177 as permitted sender) identity=mailfrom; client-ip=209.85.216.177; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="agarwal1975@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-qc0-f177.google.com) identity=helo; client-ip=209.85.216.177; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="postmaster@mail-qc0-f177.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aj4DAGnf+FLRVdixlGdsb2JhbABZg0RXqyqLP4hUgQgIFg4BAQEBBwsLCRIqgmwBGxAKBAMSEF0BEQEFASIBGgyHXAEDEQ2cWYxegw6TWAoZJw1kh2IRAQUMjm2COg+BegSJSY5igTKLLoNUGCmEdx4 X-IPAS-Result: Aj4DAGnf+FLRVdixlGdsb2JhbABZg0RXqyqLP4hUgQgIFg4BAQEBBwsLCRIqgmwBGxAKBAMSEF0BEQEFASIBGgyHXAEDEQ2cWYxegw6TWAoZJw1kh2IRAQUMjm2COg+BegSJSY5igTKLLoNUGCmEdx4 X-IronPort-AV: E=Sophos;i="4.95,818,1384297200"; d="scan'208";a="48485147" Received: from mail-qc0-f177.google.com ([209.85.216.177]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 10 Feb 2014 15:21:15 +0100 Received: by mail-qc0-f177.google.com with SMTP id i8so10404025qcq.8 for ; Mon, 10 Feb 2014 06:21:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=4kft6JOahiqUU+9XCE4YeMz5yqD5AoMseGBOxSIpIdk=; b=Ru29KlR+4UBkarf0Uw1Wr6m1kOh4drPTTjiQ62UpZGvVdU/RhJ5i93X2d5tv4t2IHc OUNcXckRLbkChozSa4sNsCXkVZoYirCjWGxjBYRS/tL4EhNA0jHCQkB4uOm6liwhg5+a WU/LOawHtV9DbOe81B5cahTkY091Lj+W41FN8yelo2g0tGD/bRaeJ8xjVOfVlnyr1rM/ /IEmcY9tA8yiUxa2olXbRtWaysCL5BPd4UjHfRv9vRr0gDACC/QAgCUsmzoEDMGWXHbC MYurlJfIOAcMU3WL9b6bOpJHHmK9zuTIWrM6ihV+rcZrg94udNLR+C3U3DzHsXFdtFH4 2LBw== X-Received: by 10.224.127.73 with SMTP id f9mr19699725qas.11.1392042074734; Mon, 10 Feb 2014 06:21:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.67.131 with HTTP; Mon, 10 Feb 2014 06:20:54 -0800 (PST) From: Ashish Agarwal Date: Mon, 10 Feb 2014 09:20:54 -0500 Message-ID: To: Caml List , infrastructure Content-Type: multipart/alternative; boundary=001a11c2bcf26093ed04f20e0df1 Subject: [Caml-list] ocaml.org licensing --001a11c2bcf26093ed04f20e0df1 Content-Type: text/plain; charset=ISO-8859-1 Dear all, The content and implementation of the OCaml.org website do not have licenses specified, which should be fixed. Our goal is to encourage contributions, give appropriate credit to contributors, and maximize the utility of the website for the entire OCaml community. We would like the community's feedback on the following proposal: (A) Content is released under CC BY-SA 4.0 [1]. (B) Code that implements the site is released under the ISC license [2]. (C) Code examples within content are released under the UNLICENSE [3]. (D) Design of the site. All rights reserved by the OCaml.org project. (E) OCaml logo is released under the UNLICENSE [3]. (F) Abstracts, slides from meetings. Rights retained by contributor. Here is our reasoning for each of the above: (A) Content refers to text that is visible by readers at http://ocaml.org(except for code; see (C) below). We'd like others to be able to use these materials but we don't want to create a situation where content that is freely given to the community (which amounts to a substantive volume of work) is then taken and monetized without giving back. The CC BY-SA 4.0 license [1] allows anyone to share and adapt the work, including for commercial gain, as long as that work is also released under the same (or compatible) license. This means that commercial works could be produced but free versions would also have to be made available. Thus, the community wouldn't lose out on any derivative work. (B) Code that implements ocaml.org. We want the code implementing the site to be open source and available for others to use as they wish. Examples of this include the files found under the 'script' folder of the repository [6]. The ISC licence [2] has already been chosen for OMD and MPP, two libraries that OCaml.org relies on substantially. Additional scripts are not particularly complex in nature, and we feel their use should not be restricted. (C) Code examples within content. For example, you can see many of these on the 99 problems page [5]. These are typically small pieces of useful code and we want people to be able to use them however they see fit. We want to do this without the burden of attribution that an open source license (e.g. ISC) would require, so placing them in the public domain seems like the sensible thing to do. The UNLICENSE [3] is one way of putting works in the public domain and is how code examples in Real World OCaml are released [4]. (D) Design of the site. This is essentially the CSS, banner image, and custom logos (except the OCaml logo, see (E) below). The design uniquely identifies ocaml.org, and it would be awkward if another site looked similar. It seems sensible to reserve all rights over the design and disallow copying it in any form. (E) The new OCaml logo [7], which you see in the top-left of ocaml.org, should be encouraged. We hope this can be a unifying symbol of all things related to OCaml. Everyone should use this logo in their OCaml blogs, websites, documentation, presentations, T-shirts, stickers, etc. Thus, it should be usable freely by all, which can be achieved by releasing it under the UNLICENSE. (F) OCaml.org also hosts abstracts and slides for various meetings, such as the OCaml Users and Developers Workshop. Contributors should retain all rights over those works or be subject to whatever agreement they have with the respective meeting. They are not considered part of the Content as defined in (A). [1] http://creativecommons.org/licenses/by-sa/4.0/ [2] http://opensource.org/licenses/ISC [3] http://unlicense.org [4] https://github.com/realworldocaml/examples/blob/master/UNLICENSE [5] http://ocaml.org/learn/tutorials/99problems.html [6] https://github.com/ocaml/ocaml.org [7] http://ocaml.org/img/ocaml.png --001a11c2bcf26093ed04f20e0df1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Dear all,

The content and implementation of the OCa= ml.org website do not have licenses specified, which should be fixed. Our g= oal is to encourage contributions, give appropriate credit to contributors,= and maximize the utility of the website for the entire OCaml community. We= would like the community’s feedback on the following proposal:

(A) Content is released under CC BY-SA 4.0 [1].
(B) Code that implem= ents the site is released under the ISC license [2].
(C) Code examples w= ithin content are released under the UNLICENSE [3].
(D) Design of the si= te. All rights reserved by the OCaml.org project.
(E) OCaml logo is released under the UNLICENSE [3].
(F) Abstracts, slide= s from meetings. Rights retained by contributor.

Here is our reasoni= ng for each of the above:

(A) Content refers to text that is visible= by readers at http://ocaml.org (except fo= r code; see (C) below). We'd like others to be able to use these materi= als but we don't want to create a situation where content that is freel= y given to the community (which amounts to a substantive volume of work) is= then taken and monetized without giving back.

The CC BY-SA 4.0 license [1] allows anyone to share and adapt the work,= including for commercial gain, as long as that work is also released under= the same (or compatible) license. This means that commercial works could b= e produced but free versions would also have to be made available. Thus, th= e community wouldn't lose out on any derivative work.

(B) Code that implements ocaml.org. We= want the code implementing the site to be open source and available for ot= hers to use as they wish. Examples of this include the files found under th= e 'script' folder of the repository [6]. The ISC licence [2] has al= ready been chosen for OMD and MPP, two libraries that OCaml.org relies on s= ubstantially. Additional scripts are not particularly complex in nature, an= d we feel their use should not be restricted.

(C) Code examples within content. For example, you can see many of thes= e on the 99 problems page [5]. These are typically small pieces of useful c= ode and we want people to be able to use them however they see fit. We want= to do this without the burden of attribution that an open source license (= e.g. ISC) would require, so placing them in the public domain seems like th= e sensible thing to do. The UNLICENSE [3] is one way of putting works in th= e public domain and is how code examples in Real World OCaml are released [= 4].

(D) Design of the site. This is essentially the CSS, banner image, and = custom logos (except the OCaml logo, see (E) below). The design uniquely id= entifies ocaml.org, and it would be awkwar= d if another site looked similar. It seems sensible to reserve all rights o= ver the design and disallow copying it in any form.

(E) The new OCaml logo [7], which you see in the top-left of ocaml.org, should be encouraged. We hope this can be= a unifying symbol of all things related to OCaml. Everyone should use this= logo in their OCaml blogs, websites, documentation, presentations, T-shirt= s, stickers, etc. Thus, it should be usable freely by all, which can be ach= ieved by releasing it under the UNLICENSE.

(F) OCaml.org also hosts abstracts and slides for various meetings, suc= h as the OCaml Users and Developers Workshop. Contributors should retain al= l rights over those works or be subject to whatever agreement they have wit= h the respective meeting. They are not considered part of the Content as de= fined in (A).

[1] http://c= reativecommons.org/licenses/by-sa/4.0/
[2] http://opensource.org/licenses/ISC
[3] http://unlicense.org
[4] https://github.com/realworldocaml/examples/blob/master/UNLICENSE<= br>[5] http://= ocaml.org/learn/tutorials/99problems.html
[6] https://github.com/ocaml= /ocaml.org
[7] http://oca= ml.org/img/ocaml.png

--001a11c2bcf26093ed04f20e0df1--