mailing list of musl libc
 help / color / mirror / code / Atom feed
From: rich felker <dalias@etalabs.net>
To: musl@lists.openwall.com
Subject: Re: Weekly reports - X
Date: Sun, 26 Jun 2011 17:13:42 -0400	[thread overview]
Message-ID: <BANLkTimbzfJC5S7ZqvcfM25SFniGzNickQ@mail.gmail.com> (raw)
In-Reply-To: <4E079F22.1070901@gmail.com>

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

Luka,
I would be happy enough with LGPL, but I believe Openwall's commitment to
GSoC included terms that all the code developed under their projects would
be under BSD license (or equally/more permissive). In any case I don't think
the license matters at all for test case code. Anyone who wanted to improve
it without releasing their improvements would almost surely be using it for
internal use only (testing their implementation), not as a deployed product,
so even if it were GPL they would not be obligated to release anything.
Conversely, since it must be in source form to be useful for testing an
implementation, even under BSD license, nobody could make a useful
closed-source test product out of cluts - the source is essential to using
it! Thus I think we should just put aside this bikeshed and BSD it.

Rich




On Sun, Jun 26, 2011 at 5:05 PM, Luka Marčetić <paxcoder@gmail.com> wrote:

> Hi there.
> I'm sorry about falling behind so much. Good news though, summer brings me
> a free window that I'll be able to dedicate to cluts. This next week is the
> last one that I'll be busy with school until September. Next week, I'll
> finish format.c (and perhaps rename it to numerical.c or alike) and fix
> alloc.c(arrays instead of lists+implementing your suggestions-keep making
> them btw. i appreciate them). Things will finally pick up afterward.
> About the license: I've been quiet because I like copyleft. My preferred
> license is GPLv3+. But Solar I think said nobody is going to make their own
> proprietary version of the library, so why not just make the license
> permissive and let them use it however. Perhaps we could compromise and
> choose LGPL, the musl's license. I think the reasoning behind that
> particular license is clear.
>
> SUMMARY: 1) Serious work will start a week after this one. 2) How about
> LGPL as a compromise?
> Thanks.
> --Luka M.
>

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

  reply	other threads:[~2011-06-26 21:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 20:20 Weekly reports - B Luka Marčetić
2011-06-12 23:13 ` Rich Felker
2011-06-13  2:11 ` Solar Designer
2011-06-13  2:22   ` Rich Felker
2011-06-13  2:56     ` Solar Designer
2011-06-13  4:54       ` Rich Felker
2011-06-13  6:48         ` Solar Designer
2011-07-06 11:35         ` errno (was: Weekly reports - B) Solar Designer
2011-07-06 12:57           ` Szabolcs Nagy
2011-07-06 13:14             ` errno Solar Designer
2011-07-07  2:56           ` errno (was: Weekly reports - B) Rich Felker
2011-06-26 21:05     ` Weekly reports - X Luka Marčetić
2011-06-26 21:13       ` rich felker [this message]
2011-06-27 22:18         ` Solar Designer
2011-07-04 19:30           ` Luka Marčetić
2011-07-04 19:39             ` Rich Felker
2011-06-13  2:22   ` specification of cluts tests - code or/and data? (was: Weekly reports - B) Solar Designer
2011-06-13  9:19     ` specification of cluts tests - code or/and data? Solar Designer
2011-07-09  6:41 ` cluts repository (was: Weekly reports - B) Solar Designer
2011-07-09 11:31   ` cluts repository Solar Designer

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=BANLkTimbzfJC5S7ZqvcfM25SFniGzNickQ@mail.gmail.com \
    --to=dalias@etalabs.net \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).