From: Michael Ekstrand <michael@elehack.net>
To: caml-list@inria.fr
Subject: Gallium wiki sample code copyright and licensing
Date: Wed, 21 Jan 2009 18:51:41 -0600 [thread overview]
Message-ID: <87iqo89n8i.fsf@elehack.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
In a couple (at present undistributed) projects now, I have used the
example from the Gallium wiki on integrating ocamlfind and
ocamlbuild[1].
I do not, however, find any kind of copyright notice or licensing terms
in the wiki. While it seems reasonable to assume that example code like
this on a publicly-editable site is intended for general use, re-use,
and integration, it would be comforting to have an explicit licensing
terms or disavowal of copyright interests or so that I can know my code
trees are copyright-clean. Can anyone here speak to the copyright
status of content in the wiki, and in particular this example?
Thanks,
- Michael
1. http://brion.inria.fr/gallium/index.php/Using_ocamlfind_with_ocamlbuild
--
mouse, n: A device for pointing at the xterm in which you want to type.
Confused by the strange files? I cryptographically sign my messages.
For more information see <http://www.elehack.net/resources/gpg>.
[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]
reply other threads:[~2009-01-22 0:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87iqo89n8i.fsf@elehack.net \
--to=michael@elehack.net \
--cc=caml-list@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