From: Michael Haggerty <mhagger@alum.mit.edu>
To: git discussion list <git@vger.kernel.org>,
Andy Parkins <andyparkins@gmail.com>
Cc: mhagger/git-multimail
<reply+i-10159725-60cb2c338c594bd09d77fe2f8d628aa55114a3f6-119718@reply.github.com>,
Michiel Holtkamp <notifications@github.com>
Subject: Re: [git-multimail] License unknown (#1)
Date: Sun, 27 Jan 2013 19:52:58 +0100 [thread overview]
Message-ID: <5105778A.1040401@alum.mit.edu> (raw)
In-Reply-To: <mhagger/git-multimail/issues/1/12754195@github.com>
I have a question about the license of contrib/hooks/post-commit-email.
I had assumed that since it is in the git project, which is GPLv2, and
since it contains no contrary information, it would by implication also
fall under GPLv2. But the file itself contains no explicit license
information, and it is not clear to me that the "signed-off-by" line
implies a particular license, either. (The signed-off-by *does* seem to
imply that the source code is under some kind of open source license,
but not which one.)
If somebody can explain what license the code is under and how they come
to that conclusion, I would be very grateful.
And if Andy Parkins (the original author) is listening, please indicate
whether you had any intent *other* than GPLv2.
For anybody who is interested, the file was first committed in
4557e0de5b and has been modified by several authors since then.
Given the pretty clear open-sourciness of the script, I don't think this
has to be made into a big issue. But it would be nice to state the
license explicitly for future users' information.
Thanks,
Michael
On 01/27/2013 02:38 PM, Michiel Holtkamp wrote:
> Actually, I'm not sure that it is GPLv2 for the original script. The
> COPYING file in the main project declares the project as GPLv2, but it
> also says that people contributing should make their preferences (for
> licensing) known. Maybe we can assume it's GPLv2, (as the original
> writer might have assumed it was GPLv2), but it's not explicitly stated
> so I'm not sure (IANAL).
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next parent reply other threads:[~2013-01-27 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mhagger/git-multimail/issues/1@github.com>
[not found] ` <mhagger/git-multimail/issues/1/12754195@github.com>
2013-01-27 18:52 ` Michael Haggerty [this message]
[not found] ` <511A04DA.7010809@alum.mit.edu>
2013-02-12 15:11 ` Fwd: Re: [git-multimail] License unknown (#1) Andy Parkins
2013-02-12 15:28 ` Andy Parkins
2013-02-13 12:10 ` Michael Haggerty
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=5105778A.1040401@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=notifications@github.com \
--cc=reply+i-10159725-60cb2c338c594bd09d77fe2f8d628aa55114a3f6-119718@reply.github.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.
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).