From: Kaspar Rohrer <kaspar.rohrer@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Inspect libary
Date: Thu, 15 Apr 2010 12:42:37 +0200 [thread overview]
Message-ID: <2D329B0F-E57C-4449-949C-DB0D9D64F2DE@gmail.com> (raw)
Hi everybody
Thanks for all the feedback and suggestions regarding hosting and licensing of my little library. I think I will host the code on github, because I really like the clean and shiny UI.
As for the license, I'm strongly favoring the LGPL license ATM, but I am unsure whether I should go with version 2.1 or 3.0. And whether or not I need to add a linking exception. Any opinions on that?
I'm currently documenting the source code and should be ready to release this evening.
Thanks
Kaspar Rohrer
PS: Does somebody know why all of my browsers (Firefox, Safari, Camino on OS X 10.6) do not recognize the Forge.ocamlcore.org server certificate?
next reply other threads:[~2010-04-15 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 10:42 Kaspar Rohrer [this message]
2010-04-15 10:53 ` [Caml-list] " Vincent Aravantinos
2010-04-15 11:23 ` Sylvain Le Gall
2010-04-15 19:45 ` [Caml-list] " Ashish Agarwal
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=2D329B0F-E57C-4449-949C-DB0D9D64F2DE@gmail.com \
--to=kaspar.rohrer@gmail.com \
--cc=caml-list@yquem.inria.fr \
/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;
as well as URLs for NNTP newsgroup(s).