Re: [notmuch] Using test-lib.sh under GPLv3?
Hi, On Fri, 19 Feb 2010, Michal Sojka wrote: as you can read bellow, I'd like to use git's test-lib.sh in a GPLv3 project. Do you mind if I use your work in that file under GPLv3? I do not mind, but I would like to ask that you contribute the improvements back under GPLv2. Thanks, Johannes ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: [notmuch] Using test-lib.sh under GPLv3?
Hi, On Fri, 19 Feb 2010, Carl Worth wrote: On Fri, 19 Feb 2010 11:39:04 +0100 (CET), Johannes Schindelin johannes.schinde...@gmx.de wrote: On Fri, 19 Feb 2010, Michal Sojka wrote: as you can read bellow, I'd like to use git's test-lib.sh in a GPLv3 project. Do you mind if I use your work in that file under GPLv3? I do not mind, but I would like to ask that you contribute the improvements back under GPLv2. Thanks everyone for your agreement. And yes, we'll contribute back any improvements under GPLv2. I think the most clear step forward would be for test-lib.sh to be updated in the git repository with an explicit licensing blurb reflecting this agreement. Sure. If you make an appropriate patch, I'll ACK it. Ciao, Dscho ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[notmuch] Using test-lib.sh under GPLv3?
Hi, On Fri, 19 Feb 2010, Michal Sojka wrote: > as you can read bellow, I'd like to use git's test-lib.sh in a GPLv3 > project. Do you mind if I use your work in that file under GPLv3? I do not mind, but I would like to ask that you contribute the improvements back under GPLv2. Thanks, Johannes
[notmuch] Using test-lib.sh under GPLv3?
Hi, On Fri, 19 Feb 2010, Carl Worth wrote: > On Fri, 19 Feb 2010 11:39:04 +0100 (CET), Johannes Schindelin > wrote: > > On Fri, 19 Feb 2010, Michal Sojka wrote: > > > > > as you can read bellow, I'd like to use git's test-lib.sh in a GPLv3 > > > project. Do you mind if I use your work in that file under GPLv3? > > > > I do not mind, but I would like to ask that you contribute the > > improvements back under GPLv2. > > Thanks everyone for your agreement. > > And yes, we'll contribute back any improvements under GPLv2. > > I think the most clear step forward would be for test-lib.sh to be > updated in the git repository with an explicit licensing blurb > reflecting this agreement. Sure. If you make an appropriate patch, I'll ACK it. Ciao, Dscho
[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.
Hi, On Sat, 20 Feb 2010, Carl Worth wrote: > This file has had no explicit license information noted in it, but > has clearly been created and modified according to the terms of GPLv2 > as with the rest of the git code base. > > The purpose of relicensing is to allow other GPLv3+ projects (in > particular, the notmuch project: http://notmuchmail.org) to use this > same test-suite structure (and to contribute changes back as well). > > The request for relicensing was presented to the git community in: > > Message-ID: <871vgmki4f.fsf at steelpick.localdomain> > > and explicitly agreed to by Junio C Hamano, Sverre Rabbelier, Johannes > Schindelin, Pierre Habouzit, and Johannes Sixt. As promised: Acked-by: Johannes Schindelin Ciao, Dscho
[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.
Hi, On Tue, 23 Feb 2010, Tay Ray Chuan wrote: > On Tue, Feb 23, 2010 at 11:42 AM, Junio C Hamano > wrote: > > FWIW, I only said "_at least_ you need consent from them", and it was > > not meant to be an exhaustive list. ?"blame -C -C -C" may tell you > > more. > > Without substantial analysis, "blame" alone is not sufficient - it does > not show which work was original, or derivative. Well, I think that blame can get you very, very far. For example, you will see that Josh Triplett's only (surviving) contribution to test-lib.sh is a single line saying "unset MAIL", which is too trivial to be copyrightable (and if it was not trivial, it still would be the only way to accomplish what it does, so it is again not copyrightable). Ciao, Dscho
