Licensing problems in octave-forge pkgs

View: New views
14 Messages — Rating Filter:   Alert me  

Licensing problems in octave-forge pkgs

by Rafael Laboissiere :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Several octave-forge packages have been updated to Debian unstable and are
waiting in the NEW queue [1] for ftp-master approval.

In building the Debian packages, we found some licensing problems.  We are
maintaining a TODO file with the list of issues, available in our SVN
repository [2] (you will find below the current version of this file).  Some
of these problems have been already reported and discussed in octave-dev.

We decided to go ahead and upload the packages despite of the above,
essentially because we believe these are not real problems, just cases
needing clarifications.

We thank the octave-dev developers in advance for fixing the issues listed.

[1] http://ftp-master.debian.org/new.html
[2] http://svn.debian.org/wsvn/pkg-octave/octave-forge-pkgs/TODO?op=file&rev=0&sc=0

Rafael


======================================================================
copyright stuff (things that still need some review)

audio:
        aurecord.1 (Dirk Edenbuettel)
        endpoint.doc (?)
        sample.wav (GPL is not a good idea, unless that file was created with a hex editor)
        src/Make*

communications:
        doc/comms.pdf (no source shipped (included in SVN)? => mail sent to octave-forge list)
        inst/doc.info (same)

econometrics:
        kernel_density_cvscore.m (no license statement)
        kernel_regression_cvscore (ditto)
fixed

general:
        inst/fcnchk.m (trivial fucntion, no copyright statement)

gsl:
        src/double_double_to_double.cc.template,
        src/int_int_double_to_double.cc.template,
        src/double_mode_to_double.cc.template,
        src/int_to_double.cc.template
        src/double_to_double.cc.template,
        src/int_double_to_double.cc.template
        (no copyright statement)

image:
        src/__magick_read__.cc (no copyright statement)

        bwimage.cc (no license conditions)

linear-algebra:
        src/test_gsvd.m (no copyright statement, it is just a test script)

miscellaneous:
        inst/grep.m, inst/inz.m, inst/nze.m, src/octave.dtd,
        src/listencanfork.c (no copyright statement)

        src/listen.cc (no copyright statement, contains code taken
        from the Unix Programming FAQ, Copyright © 2000 Andrew
        Gierth, but without license conditions)

nnet:
        doc/pdf/neuralNetworkToolboxForOctaveUsersGuide.pdf (no
        copyright statement, no sources)

octcdf:
        inst/example_netcdf.m, inst/example_opendap.m (no copyright statement)

odepkg:
        inst/doc.info (no copyright owner, no sources)

optim:
        inst/wsolve.m (no copyright owner)

        doc/mintoolkit.pdf (no copyright statement, no sources)

        doc/optim-mini-howto-2.pdf (no copyright year, no sources;
        it's GFDL, is it DFSG-compatible?)

optiminterp:
        inst/example_optiminterp.m (no copyright statement)

parallel:
        src/swab.h (no copyright statement)

plot:
        inst/zoom.m (dummy file; I think it is okay to distribute
        it without copyright statement)

        src/grab.cc, src/gpick.cc
        These files contain the statement
         * This contains bits of code hacked from the
         * X Consortium and from Octave. Please see the
         * appropriate licences. The rest is mine, and
         * you can do what you want with that part.
        What should we do?

        inst/ginput.m (seems to be GPL, but has unclear statement)

signal:
        inst/flattopwin.m (file in public domain but without copyright
        statement)
        inst/hann.m (one-line function without copyright statement)

sockets:
        src/sockets.cc (no copyright statement; should we assume the
        same as in DESCRITPION?)

symbolic:
        doc/symbolic.html (no source and/or no copyright statement)

vrml:
        doc/vrml-mini-howto-1.pdf (no source)


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by David Bateman :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Rafael Laboissiere wrote:

> Several octave-forge packages have been updated to Debian unstable and are
> waiting in the NEW queue [1] for ftp-master approval.
>
> In building the Debian packages, we found some licensing problems.  We are
> maintaining a TODO file with the list of issues, available in our SVN
> repository [2] (you will find below the current version of this file).  Some
> of these problems have been already reported and discussed in octave-dev.
>
> We decided to go ahead and upload the packages despite of the above,
> essentially because we believe these are not real problems, just cases
> needing clarifications.
>
> We thank the octave-dev developers in advance for fixing the issues listed.
>
> [1] http://ftp-master.debian.org/new.html
> [2] http://svn.debian.org/wsvn/pkg-octave/octave-forge-pkgs/TODO?op=file&rev=0&sc=0
>
> Rafael
>  
If the issues are license clarification, then only the original author
can correspond.. It will therefore be extremely difficult to address
this list of clarifications. However, it has always been assumed that
short, uncopyrighted functions in octave-forge were public domain. Also
if the packages include a COPYING file which that are obliged to with
the Octave package manager, then doesn't that determine th licensing
conditions for the unlicensed files?

D.


--
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph)
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob)
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax)

The information contained in this communication has been classified as:

[x] General Business Information
[ ] Motorola Internal Use Only
[ ] Motorola Confidential Proprietary


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by Søren Hauberg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

fre, 18 04 2008 kl. 14:49 +0200, skrev Rafael Laboissiere:
> In building the Debian packages, we found some licensing problems.  We are
> maintaining a TODO file with the list of issues, available in our SVN
> repository [2] (you will find below the current version of this file).  Some
> of these problems have been already reported and discussed in octave-dev.
[snip]
> image:
>         src/__magick_read__.cc (no copyright statement)
>
>         bwimage.cc (no license conditions)

I can't find the 'bwimage.cc' file. Where is it located?

Søren


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by Rafael Laboissiere :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

* David Bateman <David.Bateman@...> [2008-04-18 15:03]:

> If the issues are license clarification, then only the original author
> can correspond.. It will therefore be extremely difficult to address
> this list of clarifications.

Okay, let us hope that the original authors will react.

> However, it has always been assumed that short, uncopyrighted functions in
> octave-forge were public domain.

Okay, but this should be stated somewhere in the tarballs.

> Also if the packages include a COPYING file which that are obliged to with
> the Octave package manager, then doesn't that determine th licensing
> conditions for the unlicensed files?

Yes, but some files lack the "Copyright (C) YYYY" notices, which can not be
guessed easily in a multi-author package.

--
Rafael

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by Andy Adler-8 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 18/04/2008, Rafael Laboissiere <rafael@...> wrote:
>  plot:
>         src/grab.cc, src/gpick.cc
>         These files contain the statement
>          * This contains bits of code hacked from the
>          * X Consortium and from Octave. Please see the
>          * appropriate licences. The rest is mine, and
>          * you can do what you want with that part.
>         What should we do?

These files are mine. I used examples from X and Octave when
I wrote them, and my code is in the public domain.

Is that clear?
--
Andy Adler <adler@...> +1-613-520-2600x8785

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by Thomas Weber-8 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 18/04/08 15:16 +0200, Søren Hauberg wrote:

> fre, 18 04 2008 kl. 14:49 +0200, skrev Rafael Laboissiere:
> > In building the Debian packages, we found some licensing problems.  We are
> > maintaining a TODO file with the list of issues, available in our SVN
> > repository [2] (you will find below the current version of this file).  Some
> > of these problems have been already reported and discussed in octave-dev.
> [snip]
> > image:
> >         src/__magick_read__.cc (no copyright statement)
> >
> >         bwimage.cc (no license conditions)
>
> I can't find the 'bwimage.cc' file. Where is it located?

My bad, the filename is bwlabel.cc (from image/src) and it says:
====================================================================
    bwimage.cc - octave module to label componenets of a binary image

        copyright 2002 Jeffrey E. Boyd
====================================================================

        Thomas

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by Rafael Laboissiere :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

* Rafael Laboissiere <rafael@...> [2008-04-18 14:49]:

> Several octave-forge packages have been updated to Debian unstable and are
> waiting in the NEW queue [1] for ftp-master approval.
>
> In building the Debian packages, we found some licensing problems.  We are
> maintaining a TODO file with the list of issues, available in our SVN
> repository [2] (you will find below the current version of this file).  Some
> of these problems have been already reported and discussed in octave-dev.
>
> We decided to go ahead and upload the packages despite of the above,
> essentially because we believe these are not real problems, just cases
> needing clarifications.

Several packages have been accepted yesterday and are waiting in the
incoming area [1].  It seems that the lacking copyright notice and/or
licensing terms are not that problematic.  However, six packages got
rejected (communications [2], fixed [3], nnet [4], odepkg [5], optim [6],
and vrml [7]) because the sources for the PDF and info files are missing in
the tarballs.

We (the DOG) will try to fix the problems by including the sources taken
from SVN into the Debian source packages, but it would be good to fix it
upstream.

[1] http://qa.debian.org/developer.php?login=pkg-octave-devel@...
[2] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003807.html
[3] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003819.html
[4] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003827.html
[5] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003822.html
[6] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003817.html
[7] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003862.html

--
Rafael

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by David Bateman :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Rafael Laboissiere wrote:

> * Rafael Laboissiere <rafael@...> [2008-04-18 14:49]:
>
>  
>> Several octave-forge packages have been updated to Debian unstable and are
>> waiting in the NEW queue [1] for ftp-master approval.
>>
>> In building the Debian packages, we found some licensing problems.  We are
>> maintaining a TODO file with the list of issues, available in our SVN
>> repository [2] (you will find below the current version of this file).  Some
>> of these problems have been already reported and discussed in octave-dev.
>>
>> We decided to go ahead and upload the packages despite of the above,
>> essentially because we believe these are not real problems, just cases
>> needing clarifications.
>>    
>
> Several packages have been accepted yesterday and are waiting in the
> incoming area [1].  It seems that the lacking copyright notice and/or
> licensing terms are not that problematic.  However, six packages got
> rejected (communications [2], fixed [3], nnet [4], odepkg [5], optim [6],
> and vrml [7]) because the sources for the PDF and info files are missing in
> the tarballs.
>
> We (the DOG) will try to fix the problems by including the sources taken
> from SVN into the Debian source packages, but it would be good to fix it
> upstream.
>
> [1] http://qa.debian.org/developer.php?login=pkg-octave-devel@...
> [2] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003807.html
> [3] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003819.html
> [4] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003827.html
> [5] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003822.html
> [6] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003817.html
> [7] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003862.html
>
>  
The communications and fixed packages are already fixed upstream. If the
authors of nnet, odepkg, optim and vrml don't include the sources
themselves to the PDF file I'll make sure its done before the next release.

D.


--
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph)
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob)
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax)

The information contained in this communication has been classified as:

[x] General Business Information
[ ] Motorola Internal Use Only
[ ] Motorola Confidential Proprietary


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by David Bateman :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Andy Adler wrote:

> On 18/04/2008, Rafael Laboissiere <rafael@...> wrote:
>  
>>  plot:
>>         src/grab.cc, src/gpick.cc
>>         These files contain the statement
>>          * This contains bits of code hacked from the
>>          * X Consortium and from Octave. Please see the
>>          * appropriate licences. The rest is mine, and
>>          * you can do what you want with that part.
>>         What should we do?
>>    
>
> These files are mine. I used examples from X and Octave when
> I wrote them, and my code is in the public domain.
>
> Is that clear?
>  
The grab.cc and gpick.cc is gone in the SVN in any case.. It didn't work
with the latest gnuplot versions that trap the mouse events themselves
and was X11 specific.. These functions were replaced with m-files of
ginput.m, gtext.m and waitforbuttonpress.m that use gnuplot itself to
management the mouse events that are under a GPL v3 license..

D.

--
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph)
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob)
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax)

The information contained in this communication has been classified as:

[x] General Business Information
[ ] Motorola Internal Use Only
[ ] Motorola Confidential Proprietary


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by David Bateman :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

David Bateman wrote:

> Rafael Laboissiere wrote:
>  
>> Several packages have been accepted yesterday and are waiting in the
>> incoming area [1].  It seems that the lacking copyright notice and/or
>> licensing terms are not that problematic.  However, six packages got
>> rejected (communications [2], fixed [3], nnet [4], odepkg [5], optim [6],
>> and vrml [7]) because the sources for the PDF and info files are missing in
>> the tarballs.
>>
>> We (the DOG) will try to fix the problems by including the sources taken
>> from SVN into the Debian source packages, but it would be good to fix it
>> upstream.
>>
>> [1] http://qa.debian.org/developer.php?login=pkg-octave-devel@...
>> [2] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003807.html
>> [3] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003819.html
>> [4] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003827.html
>> [5] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003822.html
>> [6] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003817.html
>> [7] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003862.html
>>
>>  
>>    
> The communications and fixed packages are already fixed upstream. If the
> authors of nnet, odepkg, optim and vrml don't include the sources
> themselves to the PDF file I'll make sure its done before the next release.
>
> D.
>
>
>  
Ok, it was trivial to do this.. The nnet, odepkg, optim and vrml
packages all include the source files for their documentation in the SVN
of octave-forge..

D.


--
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph)
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob)
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax)

The information contained in this communication has been classified as:

[x] General Business Information
[ ] Motorola Internal Use Only
[ ] Motorola Confidential Proprietary


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by Rafael Laboissiere :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

* David Bateman <David.Bateman@...> [2008-04-21 10:40]:

> David Bateman wrote:
> > The communications and fixed packages are already fixed upstream. If the
> > authors of nnet, odepkg, optim and vrml don't include the sources
> > themselves to the PDF file I'll make sure its done before the next release.
> >  
> Ok, it was trivial to do this.. The nnet, odepkg, optim and vrml
> packages all include the source files for their documentation in the SVN
> of octave-forge..

Thanks.  Are you planning to release new versions of these packages?  If it
will be done soon, I will wait for it instead of patching the Debian
packages.
 
--
Rafael

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by David Bateman :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Rafael Laboissiere wrote:

> * David Bateman <David.Bateman@...> [2008-04-21 10:40]:
>
>  
>> David Bateman wrote:
>>    
>>> The communications and fixed packages are already fixed upstream. If the
>>> authors of nnet, odepkg, optim and vrml don't include the sources
>>> themselves to the PDF file I'll make sure its done before the next release.
>>>  
>>>      
>> Ok, it was trivial to do this.. The nnet, odepkg, optim and vrml
>> packages all include the source files for their documentation in the SVN
>> of octave-forge..
>>    
>
> Thanks.  Are you planning to release new versions of these packages?  If it
> will be done soon, I will wait for it instead of patching the Debian
> packages.
>  
>  
We're waiting for an Octave 3.0.1 release before doing it.. Therefore a
still a couple of outstanding issues before a release including

* Patch for tukeywin sent to list, needs considering
* Need to fix mingw build of fixed package prior to a release
* See if I can't get the java package to work with jre 1.7.0 on an
x86_64 linux machine (on a quick test I didn't)
* -fPIC flags in SWIG based packages still don't seem to be quite right..

Anyone want to look at any of the above I'd appreciate it..

Regards
David

--
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph)
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob)
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax)

The information contained in this communication has been classified as:

[x] General Business Information
[ ] Motorola Internal Use Only
[ ] Motorola Confidential Proprietary


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by Søren Hauberg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

fre, 18 04 2008 kl. 18:53 +0200, skrev Thomas Weber:

> > >         bwimage.cc (no license conditions)
> >
> > I can't find the 'bwimage.cc' file. Where is it located?
>
> My bad, the filename is bwlabel.cc (from image/src) and it says:
> ====================================================================
>     bwimage.cc - octave module to label componenets of a binary image
>
>         copyright 2002 Jeffrey E. Boyd
> ====================================================================

Sorry about the late reply. Assuming we'll have a release in the next
couple of days, I won't have time to attend to this problem. By the next
release I can reimplement this function (it shouldn't be too hard) and
release it under the GPL. Is this okay, or do I need to implement the
function before we make the next release?

Søren


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Licensing problems in octave-forge pkgs

by Alexander Barth-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Rafael,
Sorry for my late reply. I added a copyright statement and license
(GPL2 or later) to the files I wrote:

octcdf:
       inst/example_netcdf.m, inst/example_opendap.m (no copyright statement)

optiminterp:
       inst/example_optiminterp.m (no copyright statement)

This is fixed thus in octcdf 1.0.10 and and optiminterp 0.3.1.

Thanks and regards
Alex


On Fri, Apr 18, 2008 at 2:49 PM, Rafael Laboissiere <rafael@...> wrote:

> Several octave-forge packages have been updated to Debian unstable and are
> waiting in the NEW queue [1] for ftp-master approval.
>
> In building the Debian packages, we found some licensing problems.  We are
> maintaining a TODO file with the list of issues, available in our SVN
> repository [2] (you will find below the current version of this file).  Some
> of these problems have been already reported and discussed in octave-dev.
>
> We decided to go ahead and upload the packages despite of the above,
> essentially because we believe these are not real problems, just cases
> needing clarifications.
>
> We thank the octave-dev developers in advance for fixing the issues listed.
>
> [1] http://ftp-master.debian.org/new.html
> [2] http://svn.debian.org/wsvn/pkg-octave/octave-forge-pkgs/TODO?op=file&rev=0&sc=0
>
> Rafael
>
>
> ======================================================================
> copyright stuff (things that still need some review)
>
> audio:
>        aurecord.1 (Dirk Edenbuettel)
>        endpoint.doc (?)
>        sample.wav (GPL is not a good idea, unless that file was created with a hex editor)
>        src/Make*
>
> communications:
>        doc/comms.pdf (no source shipped (included in SVN)? => mail sent to octave-forge list)
>        inst/doc.info (same)
>
> econometrics:
>        kernel_density_cvscore.m (no license statement)
>        kernel_regression_cvscore (ditto)
> fixed
>
> general:
>        inst/fcnchk.m (trivial fucntion, no copyright statement)
>
> gsl:
>        src/double_double_to_double.cc.template,
>        src/int_int_double_to_double.cc.template,
>        src/double_mode_to_double.cc.template,
>        src/int_to_double.cc.template
>        src/double_to_double.cc.template,
>        src/int_double_to_double.cc.template
>        (no copyright statement)
>
> image:
>        src/__magick_read__.cc (no copyright statement)
>
>        bwimage.cc (no license conditions)
>
> linear-algebra:
>        src/test_gsvd.m (no copyright statement, it is just a test script)
>
> miscellaneous:
>        inst/grep.m, inst/inz.m, inst/nze.m, src/octave.dtd,
>        src/listencanfork.c (no copyright statement)
>
>        src/listen.cc (no copyright statement, contains code taken
>        from the Unix Programming FAQ, Copyright (c) 2000 Andrew
>        Gierth, but without license conditions)
>
> nnet:
>        doc/pdf/neuralNetworkToolboxForOctaveUsersGuide.pdf (no
>        copyright statement, no sources)
>
> octcdf:
>        inst/example_netcdf.m, inst/example_opendap.m (no copyright statement)
>
> odepkg:
>        inst/doc.info (no copyright owner, no sources)
>
> optim:
>        inst/wsolve.m (no copyright owner)
>
>        doc/mintoolkit.pdf (no copyright statement, no sources)
>
>        doc/optim-mini-howto-2.pdf (no copyright year, no sources;
>        it's GFDL, is it DFSG-compatible?)
>
> optiminterp:
>        inst/example_optiminterp.m (no copyright statement)
>
> parallel:
>        src/swab.h (no copyright statement)
>
> plot:
>        inst/zoom.m (dummy file; I think it is okay to distribute
>        it without copyright statement)
>
>        src/grab.cc, src/gpick.cc
>        These files contain the statement
>         * This contains bits of code hacked from the
>         * X Consortium and from Octave. Please see the
>         * appropriate licences. The rest is mine, and
>         * you can do what you want with that part.
>        What should we do?
>
>        inst/ginput.m (seems to be GPL, but has unclear statement)
>
> signal:
>        inst/flattopwin.m (file in public domain but without copyright
>        statement)
>        inst/hann.m (one-line function without copyright statement)
>
> sockets:
>        src/sockets.cc (no copyright statement; should we assume the
>        same as in DESCRITPION?)
>
> symbolic:
>        doc/symbolic.html (no source and/or no copyright statement)
>
> vrml:
>        doc/vrml-mini-howto-1.pdf (no source)
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
>

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev