From: Andreas Ericsson <ae@op5.se>
To: Martin Koegler <mkoegler@auto.tuwien.ac.at>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git to libgit2 code relicensing
Date: Fri, 14 Nov 2008 23:56:30 +0100 [thread overview]
Message-ID: <491E021E.5020104@op5.se> (raw)
In-Reply-To: <20081114213352.GA12134@auto.tuwien.ac.at>
Martin Koegler wrote:
> On Fri, Nov 14, 2008 at 09:59:56PM +0100, Andreas Ericsson wrote:
>> I've put everyone who "owns" more than 500 lines of code
>> on the bcc list, figuring your permission is important
>> but that you don't want the hundreds (well, one can hope)
>> of emails from people saying "ok". The list of major owners
>> was generated with "git showners *.c" in a worktree from
>> the next branch of git.git.
>
> I don't think, that your way for relicensing is bullet proof:
>
I know that it's not, which is why I'm doing research to take care
of the pieces interesting for libgit2 that could possibly have
been derived from elsewhere. Reading and filling structures specific
to git is something I'd be surprised if they originated outside of
git though.
> I consider many of my GIT patches as derived work from other parts of
> GIT, even if git blame is stating me as author. I can gurantee you,
> that I comply with the "Developer's Certificate of Origin 1.1" point
> b, as its based on code out of git.git.
Right, but if we can never re-use code from git.git, libgit will never
fly. It's unfortunately as simple as that. So perhaps we're left with
the option of writing a GPL'd library or just go hang.
> But I can't tell you, from which files I reused code anymore.
>
To a certain point, "git blame" can.
> Probably other people did the same.
>
> Your method is ignoring such derived code.
>
Right. If possible, I'd still like an OK from you though. If nothing
else, it'll make it possible to re-use code that originated from
someone else and that you changed, assuming that "someone else" also
agree to relicensing their code. With 100% of the authors agreeing
to that, we could have a libified git flying in a matter of months
instead of never.
It's unfortunate if the letter of the law pertaining to a particular
license should prevent the copyright owners from doing whatever
they want with the code, but perhaps that's the world we live in.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-11-14 22:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 20:59 git to libgit2 code relicensing Andreas Ericsson
2008-11-14 21:33 ` Martin Koegler
2008-11-14 21:46 ` Sverre Rabbelier
2008-11-14 22:57 ` Andreas Ericsson
2008-11-14 22:56 ` Andreas Ericsson [this message]
2008-11-15 17:13 ` Martin Koegler
2008-11-14 23:13 ` Linus Torvalds
2008-11-14 23:46 ` Shawn O. Pearce
2008-11-15 4:30 ` David Brown
2008-11-15 5:00 ` Shawn O. Pearce
2008-11-15 8:04 ` Nicolas Pitre
2008-11-15 18:39 ` David Brown
2008-11-15 12:39 ` Miklos Vajna
2008-11-15 13:00 ` Junio C Hamano
2008-11-15 19:33 ` Miklos Vajna
2008-11-15 22:12 ` Pierre Habouzit
2008-11-15 18:49 ` David Brown
2008-11-15 16:39 ` Linus Torvalds
2008-11-15 10:17 ` Andreas Ericsson
2008-11-15 10:28 ` Pau Garcia i Quiles
2008-11-15 11:05 ` Andreas Ericsson
2008-11-15 11:33 ` Pau Garcia i Quiles
2008-11-15 11:52 ` Andreas Ericsson
2008-11-15 18:53 ` David Brown
2008-11-16 1:30 ` Daniel Barkalow
[not found] ` <200811151615.42345.chriscool@tuxfamily.org>
2008-11-16 11:50 ` Andreas Ericsson
2008-11-16 21:00 ` Johannes Schindelin
2008-11-16 21:09 ` Sverre Rabbelier
2008-11-17 7:24 ` Andreas Ericsson
2008-11-17 15:40 ` Shawn O. Pearce
2008-11-17 21:44 ` Andreas Ericsson
2008-11-20 17:41 ` René Scharfe
2008-11-25 15:19 ` Kristian Høgsberg
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=491E021E.5020104@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=mkoegler@auto.tuwien.ac.at \
/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).