Dear Junio,

I like the simple and powerful test suite used by Git and I would like
to use something like that in Notmuch project (http://notmuchmail.org/).
Notmuch is licenced under GPLv3 and we think that things will be simpler
if everything in the repository is licenced the same. You are mentioned
as a copyright holder in test-lib.sh and t0000-basic.sh so I'd like to
ask you: Would you mind using parts of these files under GPLv3?

You can see the patches for how I'd like to use these files at
http://notmuchmail.org/pipermail/notmuch/2010/thread.html#1431

Thanks,
Michal
--

[ message continues ]

Have you thought about using TAP (Test Anything Protocol) format for
your testsuite?  Its page (http://testanything.org) has a TAP-producing
bash library: http://testanything.org/wiki/index.php/Tap-functions

-- 
Jakub Narebski
Poland
ShadeHawk on #git
--

[ message continues ]

Yes, somebody has mentiond TAP on notmuch list. From a quick look at TAP
shell library it seems to me a bit more complex then git's library and
it also requires bash.

If we need to use some TAP-based tools, we could easily change the
output of git's library to conform to TAP. Right?

Michal
--

[ message continues ]

Another TAP-like option is wvtest:

   http://github.com/apenwarr/wvtest

It's LGPLv2.

Have fun,

Avery
--

[ message continues ]

Or better yet improve git test suite, so when passed --tap parameter
it would produce TAP output, instead of its own report format.  And
send patches here.

-- 
Jakub Narebski
Poland
--

[ message continues ]

I don't mind for the parts I wrote, which is the basic infrastructure
(output redirection, skipping certain tests, expecting failure, etc).
My blessing would be enough to relicense it if you are are going to take
the file from some old version like 04ece59 (GIT_SKIP_TESTS: allow users
to omit tests that are known to break, 2006-12-28) and base your work on
it, but otherwise it would not be nearly sufficient.

Other people worked on polishing it over time and they all hold copyright
on their parts.  Notable parts that are not mine and that are not git
specific are:

 - color output support is mostly by Pierre Habouzit <madcoder@debian.org>
 - valgrind support: Johannes Schindelin <johannes.schindelin@gmx.de>
 - conditional test: Johannes Sixt <j6t@kdbg.org>
 - summarizing the results: Sverre Rabbelier <srabbelier@gmail.com>

--

[ message continues ]

Dear Pierre, Johannes (2x) and Sverre,

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?

Thanks
Michal


--

[ message continues ]

Heya,


I don't mind, go right ahead :).

-- 
Cheers,

Sverre Rabbelier
--

[ message continues ]

Hi,


I do not mind, but I would like to ask that you contribute the 
improvements back under GPLv2.

Thanks,
Johannes

--

[ message continues ]

Same for me.

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org
--

[ message continues ]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLft//6JDdNq8qSWgRAsnWAJ9kJ0HbT1dZMdA694l8gJskTAocHgCfYy0e
tObx6v2wRUzboKeGhCXjTQA=
=WSgi
-----END PGP SIGNATURE-----
[ message continues ]

Hi,


Sure. If you make an appropriate patch, I'll ACK it.

Ciao,
Dscho
--

[ message continues ]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLgD4u6JDdNq8qSWgRAgvsAJ967kKQACADf0bMbDEiRviz3S6s3gCfU9lR
GIzZuopHNS96brdZO264JnQ=
=mdcQ
-----END PGP SIGNATURE-----
[ message continues ]

Please drop the parentheses around the last phrase (but not the last


Message-ID alone is not a good way to help people locate the request.
Please at least mention what mailing list the message was sent to; better
yet, do so like this:

  http://thread.gmane.org/gmane.mail.notmuch.general/1389/focus=140156

so that people can see the consent from the primary author (that is where
the focus is), the original request (that can be seen by looking at its
immediate parent), and messages with consent from other contributors, all

And a sign-off ;-).

Thanks.
--

[ message continues ]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLgtp46JDdNq8qSWgRAiWJAJ9rogmNhcIsqUf8yOTNCuJBH8PeLACgl3l4
WjQ+KxwJqWnLdVG6H0aZH38=
=mBnb
-----END PGP SIGNATURE-----
[ message continues ]

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.

You are the party that wants this relicensing, not me.  Please do not
burden me with excessive legwork for you, but help me a bit more

Oh, I never said "do not use message ID".  I said "message ID alone is not
good enough for most people".  Users of gmane and notmuch who know the
tool they use would benefit from having message ID, _too_, but even if you
were a user of notmuch, unless you have subscribed to the list and have
your own archive, you wouldn't be able to say "show id:frotz".
--

[ message continues ]

Hi,


Without substantial analysis, "blame" alone is not sufficient - it
does not show which work was original, or derivative.

-- 
Cheers,
Ray Chuan
--

[ message continues ]

Hi,


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
[ message continues ]

FWIW, gmane allows links of the form

http://mid.gmane.org/7vaav8hpfo.fsf@alter.siamese.dyndns.org

which have the advantage of being simple to use, and still contain the
necessary information to get the message in case gmane dies.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--

[ message continues ]

I hope you see I haven't asked you to do any additional legwork. A
suggestion was made to construct a patch, which I did. You always have

Certainly. My assumption was that in a commit message for git, readers
would naturally assume that a message ID with no additional
specification could be found in the archives of the standard git mailing
list, (which is the case here). Otherwise, I would have qualified the
message ID more specifically.

-Carl
[ message continues ]

Hi,


(of all projects, Mercurial!) take a look at Mercurial's attempt at
relicensing last year (http://mercurial.selenic.com/wiki/Relicensing):
they contacted all 300+ contributors as part of the process.

Of course, we aren't talking about relicensing the whole codebase.
However, I don't think any of the contributors agreed to assign their
work to the 5 people mentioned above (eg. under a contributor licence
agreement), so just getting the approval of them is not enough; you
need to get the approval of *all* contributors to test-lib.sh.

Here's what I get with 'git shortlog t/test-lib.sh  | grep "^[A-Z]"'

   Alex Riesen (5):
   Brandon Casey (2):
   Bryan Donlan (3):
   Carl Worth (1):
   Christian Couder (1):
   Clemens Buchacher (3):
   David Reiss (1):
   Emil Sit (1):
   Eric Wong (3):
   Fredrik Kuivinen (1):
   Gerrit Pape (1):
   Jakub Narebski (1):
   Jeff King (7):
   Johan Herland (1):
   Johannes Schindelin (14):
   Johannes Sixt (12):
   Jonathan Nieder (1):
   Josh Triplett (1):
   Junio C Hamano (57):
   Lea Wiemann (5):
   Markus Heidelberg (1):
   Martin Waitz (1):
   Matthew Ogilvie (1):
   Matthias Lederhofer (1):
   Michael J Gruber (4):
   Michele Ballabio (2):
   Miklos Vajna (1):
   Nicolas Pitre (1):
   Pavel Roskin (3):
   Petr Baudis (3):
   Pierre Habouzit (2):
   Robin Rosenberg (1):
   Shawn O. Pearce (4):
   Stephan Beyer (1):
   Stephen Boyd (1):
   Sverre Rabbelier (2):

PS: This message should not be construed as legal advice.

-- 
Cheers,
Ray Chuan
--

[ message continues ]

Hi,


As promised:

Acked-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>

Ciao,
Dscho
--

[ message continues ]

To all contributors to test-lib.sh mentioned in Bcc:

You're getting this message because you're recorded as contributing one
or more changes to the test-lib.sh file in the Git project, and are
therefore one of many copyright holders in the file.

We would like to extend the license of that file from GPLv2 only
license to GPLv2+ by adding the recommended "or any later version"
clause to the license. This will give us license compatibility with
GPLv3 projects, which would like to reuse test-lib.sh.

Please respond to this email with one of the following:

 YES, I agree to relicense all my contributions to test-lib.sh to GPLv2+
 with the addition of the "or any later version" clause.

 NO, I would rather not, please send me more email to convince me.

I'm putting your address to Bcc as most people are probably not
interested in receiving responses from dozens of other people. I will
track the status of received responses at
https://git.wiki.kernel.org/index.php/Test-lib_reclicensing. Please do
not remove git@vger.kernel.org when responding so that your response is
available to everyone.

Thanks!
Michal Sojka
--

[ message continues ]

Hi Michal,

I am happy for anyone to use, modify, distribute, and relicense my
meagre contribution to t/test-lib.sh in any way they please.

In particular: yes, I agree to relicense all my contributions to
test-lib.sh to GPLv2+ with the addition of the "or any later version"
clause.

Thanks,
Jonathan
--

[ message continues ]

Huh, didn't we just run through this about a month ago? Is this some
kind of stale e-mail message?

				Petr "Pasky" Baudis
--

[ message continues ]

The month ago, I didn't contact *ALL* contributors, but only the ones
with significat contribution. Now I want to finish relicensing by
contacting all contributors as sugested in some responses.

-Michal
--

[ message continues ]

Then perhaps you should exclude those who already replied earlier?
It seems to me the list on the wiki is quite similar in magnitude to
the recipient list of the last mail, surely there's no need to bother
everyone again just for few extra people?

-- 
				Petr "Pasky" Baudis
http://pasky.or.cz/ | "Ars longa, vita brevis." -- Hippocrates
--

[ message continues ]

That's exactly what I did. I excluded those who stated explicitely that
they agree. Shall I take your response as an agreement?

Michal
--

[ message continues ]

I'm not sure how you did it, but I already assented in the earlier
thread (and am listed on the wiki) and still got the mail. But anyway,
to be very clear:

   YES, I agree to relicense all my contributions to test-lib.sh to
   GPLv2+ with the addition of the "or any later version" clause.

-Peff
--

[ message continues ]

Yes. I'm afraid that E-Mail never made it to the list or to Michael, because
neither were Cc'ed. Including myself, I got positive replies from the
following contributors.

 Johan Herland
 Brandon Casey
 Petr Baudis
 Miklos Vajna
 Shawn O. Pearce

It's probably best if you guys reply here again, for the record.

Clemens
--

[ message continues ]

For the record, I'm still ok with the license change.



--

[ message continues ]

YES, I agree to relicense all my contributions to test-lib.sh to GPLv2+
with the addition of the "or any later version" clause.
--

[ message continues ]

Yes.

-- Lea
--

[ message continues ]

YES, I agree to relicense all my contributions to test-lib.sh to GPLv2+
with the addition of the "or any later version" clause.
--

[ message continues ]

YES, I agree to relicense all my contributions to test-lib.sh to GPLv2+
with the addition of the "or any later version" clause.

Clemens
--

[ message continues ]

YES, I agree to relicense all my contributions to test-lib.sh to GPLv2+
with the addition of the "or any later version" clause.
[ message continues ]

I'm fine with the change.
--

[ message continues ]

YES, I agree to relicense all my contributions to test-lib.sh to GPLv2+
with the addition of the "or any later version" clause.

Thanks,
Christian.
--

[ message continues ]

As I said earlier, I don't think my contribution is significant enough
(and large enough) to be copyrightable.  But again:

  YES, I agree to relicense all my contributions to test-lib.sh to GPLv2+
  with the addition of the "or any later version" clause.


-- 
Jakub Narebski
Poland
--

[ message continues ]

YES, I agree to relicense all my contributions to test-lib.sh to GPLv2+
with the addition of the "or any later version" clause.

--

[ message continues ]

YES, I agree to relicense all my contributions to test-lib.sh to GPLv2+
with the addition of the "or any later version" clause.

-- robin
--

[ message continues ]

On Fri, 02 Apr 2010 09:29 +0200, "Michal Sojka" <sojkam1@fel.cvut.cz>

What else do I need to do besides my acked-by to Junio's patch in
<4B8E1EBA.4090406@drmicha.warpmail.net> on 3/3?


Michael
--

[ message continues ]

Yes, the relicensing is fine with me.

             - Matthew Ogilvie
--

[ message continues ]

YES, I agree to relicense all my contributions to test-lib.sh to GPLv2+
 with the addition of the "or any later version" clause.
--

[ message continues ]

-- 
Regards,
Pavel Roskin
--

[ message continues ]

YES, I agree to relicense all my contributions to test-lib.sh to GPLv2+
with the addition of the "or any later version" clause.
-- 
Emil Sit / http://www.emilsit.net/

--

[ message continues ]

I do not mind. Go ahead.

-- Hannes
--

[