Re: Copyright for readline/editline packages

Hello, Indeed an interesting question. Although I am no licensing expert, I guess that the intention of the GPL is that if you copy the Haskell readline code which is under the GPL and modify it, then the result will also be under the GPL. Independent development is a possibility, unless you can get hold of the copyright holder. Best regards Thorkil On Saturday 12 January 2008 01:19, Judah Jacobson wrote:
Hi all,
As mentioned before, I'm putting together an editline package which will provide a subset of the APIs from the readline package, but be BSD-compatible since it links against libedit.
The licensing for the readline package itself is a little strange -- it's licensed under the GPL (because it links with libreadline), but there's no copyright holder information; and Readline.hsc from that package lists "Copyright: (c) unknown".
I'd like to put the Haskell editline package under BSD3, but most of the code will be copied verbatim from the readline package. How should this be attributed/copyrighted?
Thanks, -Judah _______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries

Thorkil Naur wrote:
Hello,
Indeed an interesting question. Although I am no licensing expert, I guess that the intention of the GPL is that if you copy the Haskell readline code which is under the GPL and modify it, then the result will also be under the GPL.
if the only copyright license granted for the Haskell-readline code is GPL (which sounds true), then it has to stay GPL. If BSD was also given as permission (it's always possible to give more permissions for the parts of something that you hold the copyright to), then, no worries, Haskell-editline can be BSD. In fact it sounds like (1) we believe the Haskell-readline code is just released under the GPL (2) we haven't even found concrete evidence that it was released with any Free license at all (although if it was released, it must be under a GPL-compatible license because it was made to link with GNU Readline, I think) The parts that cannot be written differently can be duplicated/copied anyway. I would say that attribution is a good thing (e.g. just "inspired by the Haskell-readline package" if you're making sure not to be a copyright-law "derivative work"). Finding the author would be good if we could though, because she/he/they would most likely give us BSD permissions (just guessing :-) ~Isaac

On 1/12/08, Isaac Dupree
if the only copyright license granted for the Haskell-readline code is GPL (which sounds true), then it has to stay GPL. If BSD was also given as permission (it's always possible to give more permissions for the parts of something that you hold the copyright to), then, no worries, Haskell-editline can be BSD.
[snip]
Finding the author would be good if we could though, because she/he/they would most likely give us BSD permissions (just guessing :-)
~Isaac
Thanks all, that's pretty much what I expected. I'll try to track down the author and get BSD permissions from them. I'm having trouble accessing the history of the file hslibs/util/Readline.hsc (which was deleted before the cvs->darcs change). Can I access the pre-darcs cvs repo from somewhere? The documentation for ghc-6.4 says to use glass.cse.ogi.edu, but it looks like that server is no longer active. Also, from what I can tell, several people have made minor changes to that file (such as updating to the FFI standard or adding Haddock docs). How should I handle copyright attribution and getting permission with respect to contributors? Thanks, -Judah

On 1/12/08, Judah Jacobson
I'm having trouble accessing the history of the file hslibs/util/Readline.hsc (which was deleted before the cvs->darcs change). Can I access the pre-darcs cvs repo from somewhere? The documentation for ghc-6.4 says to use glass.cse.ogi.edu, but it looks like that server is no longer active.
Never mind, I found the repo on cvs.haskell.org. -Judah

Judah Jacobson wrote:
Also, from what I can tell, several people have made minor changes to that file (such as updating to the FFI standard or adding Haddock docs). How should I handle copyright attribution and getting permission with respect to contributors?
completely mechanical changes or a single contributor contributing less than 15 lines of changes total is generally not significant for copyright.[1] The Haddock is more likely to be significant and you should probably find its author(s) too. ..although there's not very much readline docs (besides type-signatures) on http://www.haskell.org/ghc/docs/latest/html/libraries/index.html [1] http://www.gnu.org/prep/maintain/html_node/Legally-Significant.html ~Isaac

On Jan 12, 2008 11:11 AM, Judah Jacobson
On 1/12/08, Isaac Dupree
wrote: if the only copyright license granted for the Haskell-readline code is GPL (which sounds true), then it has to stay GPL. If BSD was also given as permission (it's always possible to give more permissions for the parts of something that you hold the copyright to), then, no worries, Haskell-editline can be BSD.
[snip]
Finding the author would be good if we could though, because she/he/they would most likely give us BSD permissions (just guessing :-)
~Isaac
Thanks all, that's pretty much what I expected. I'll try to track down the author and get BSD permissions from them.
An update: I determined that three people (Marcin Kowalczyk, Simon Marlow and Isaac Jones) were significant contributers to that file. All three have given their blessing towards licensing that code under BSD3. I hope to have a preliminary version of the editline package uploaded to hackage sometime later this week. Best, -Judah
participants (3)
-
Isaac Dupree
-
Judah Jacobson
-
Thorkil Naur