<div dir="ltr"><div><div><div><div><div><div><div><br></div>Hi<br><br></div>About the new logo,<br><br>- I found this page: <a href="http://ocaml.org/docs/logos.html">http://ocaml.org/docs/logos.html</a> which still references the "old" logos<br>
</div>- and, in the source there are 2 PNGs for the new one: <br> - <a href="https://github.com/ocaml/ocaml.org/blob/master/site/img/ocaml-colour.png">https://github.com/ocaml/ocaml.org/blob/master/site/img/ocaml-colour.png</a> (One day, we should converge on US Vs UK spelling BTW :) )<br>
- <a href="https://github.com/ocaml/ocaml.org/blob/master/site/img/ocaml-large.png">https://github.com/ocaml/ocaml.org/blob/master/site/img/ocaml-large.png</a><br><br></div>Is there somewhere a vector-version of the new logo? SVG or PDF?<br>
</div>(we were thinking of printing some ocaml laptop-stickers for the NYC-OCaml meetup group)<br><br><br></div>Thanks&cheers<br></div>Seb<br><br><br><div><div><div><div><br><br><br><div><br><br></div></div></div></div>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Feb 10, 2014 at 11:09 AM, Louis Gesbert <span dir="ltr"><<a href="mailto:louis.gesbert@ocamlpro.com" target="_blank">louis.gesbert@ocamlpro.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Very good move, thanks for doing this clarification !<br>
<br>
However we do have a number of contents on <a href="http://ocaml.org" target="_blank">ocaml.org</a> ; we'll need to go through them and discuss their licensing internally to give a proper response.<br>
<br>
Thanks,<br>
Louis<br>
<br>
Le lundi 10 février 2014, 09:20:54 Ashish Agarwal a écrit :<br>
<div class="">> Dear all,<br>
><br>
> The content and implementation of the OCaml.org website do not have<br>
> licenses specified, which should be fixed. Our goal is to encourage<br>
> contributions, give appropriate credit to contributors, and maximize the<br>
> utility of the website for the entire OCaml community. We would like the<br>
> community's feedback on the following proposal:<br>
><br>
> (A) Content is released under CC BY-SA 4.0 [1].<br>
> (B) Code that implements the site is released under the ISC license [2].<br>
> (C) Code examples within content are released under the UNLICENSE [3].<br>
> (D) Design of the site. All rights reserved by the OCaml.org project.<br>
> (E) OCaml logo is released under the UNLICENSE [3].<br>
> (F) Abstracts, slides from meetings. Rights retained by contributor.<br>
><br>
> Here is our reasoning for each of the above:<br>
><br>
> (A) Content refers to text that is visible by readers at<br>
</div>> <a href="http://ocaml.org" target="_blank">http://ocaml.org</a>(except for code; see (C) below). We'd like others to<br>
<div class="HOEnZb"><div class="h5">> be able to use these<br>
> materials but we don't want to create a situation where content that is<br>
> freely given to the community (which amounts to a substantive volume of<br>
> work) is then taken and monetized without giving back.<br>
><br>
> The CC BY-SA 4.0 license [1] allows anyone to share and adapt the work,<br>
> including for commercial gain, as long as that work is also released under<br>
> the same (or compatible) license. This means that commercial works could be<br>
> produced but free versions would also have to be made available. Thus, the<br>
> community wouldn't lose out on any derivative work.<br>
><br>
> (B) Code that implements <a href="http://ocaml.org" target="_blank">ocaml.org</a>. We want the code implementing the site<br>
> to be open source and available for others to use as they wish. Examples of<br>
> this include the files found under the 'script' folder of the repository<br>
> [6]. The ISC licence [2] has already been chosen for OMD and MPP, two<br>
> libraries that OCaml.org relies on substantially. Additional scripts are<br>
> not particularly complex in nature, and we feel their use should not be<br>
> restricted.<br>
><br>
> (C) Code examples within content. For example, you can see many of these on<br>
> the 99 problems page [5]. These are typically small pieces of useful code<br>
> and we want people to be able to use them however they see fit. We want to<br>
> do this without the burden of attribution that an open source license (e.g.<br>
> ISC) would require, so placing them in the public domain seems like the<br>
> sensible thing to do. The UNLICENSE [3] is one way of putting works in the<br>
> public domain and is how code examples in Real World OCaml are released [4].<br>
><br>
> (D) Design of the site. This is essentially the CSS, banner image, and<br>
> custom logos (except the OCaml logo, see (E) below). The design uniquely<br>
> identifies <a href="http://ocaml.org" target="_blank">ocaml.org</a>, and it would be awkward if another site looked<br>
> similar. It seems sensible to reserve all rights over the design and<br>
> disallow copying it in any form.<br>
><br>
> (E) The new OCaml logo [7], which you see in the top-left of <a href="http://ocaml.org" target="_blank">ocaml.org</a>,<br>
> should be encouraged. We hope this can be a unifying symbol of all things<br>
> related to OCaml. Everyone should use this logo in their OCaml blogs,<br>
> websites, documentation, presentations, T-shirts, stickers, etc. Thus, it<br>
> should be usable freely by all, which can be achieved by releasing it under<br>
> the UNLICENSE.<br>
><br>
> (F) OCaml.org also hosts abstracts and slides for various meetings, such as<br>
> the OCaml Users and Developers Workshop. Contributors should retain all<br>
> rights over those works or be subject to whatever agreement they have with<br>
> the respective meeting. They are not considered part of the Content as<br>
> defined in (A).<br>
><br>
> [1] <a href="http://creativecommons.org/licenses/by-sa/4.0/" target="_blank">http://creativecommons.org/licenses/by-sa/4.0/</a><br>
> [2] <a href="http://opensource.org/licenses/ISC" target="_blank">http://opensource.org/licenses/ISC</a><br>
> [3] <a href="http://unlicense.org" target="_blank">http://unlicense.org</a><br>
> [4] <a href="https://github.com/realworldocaml/examples/blob/master/UNLICENSE" target="_blank">https://github.com/realworldocaml/examples/blob/master/UNLICENSE</a><br>
> [5] <a href="http://ocaml.org/learn/tutorials/99problems.html" target="_blank">http://ocaml.org/learn/tutorials/99problems.html</a><br>
> [6] <a href="https://github.com/ocaml/ocaml.org" target="_blank">https://github.com/ocaml/ocaml.org</a><br>
> [7] <a href="http://ocaml.org/img/ocaml.png" target="_blank">http://ocaml.org/img/ocaml.png</a><br>
</div></div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Infrastructure mailing list<br>
<a href="mailto:Infrastructure@lists.ocaml.org">Infrastructure@lists.ocaml.org</a><br>
<a href="http://lists.ocaml.org/listinfo/infrastructure" target="_blank">http://lists.ocaml.org/listinfo/infrastructure</a><br>
</div></div></blockquote></div><br></div>