octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug tracking


From: John W. Eaton
Subject: Re: bug tracking
Date: Tue, 2 Mar 2010 18:01:51 -0500

On  2-Mar-2010, Jordi Guti rrez Hermoso wrote:

| Are you still averse to the idea of merging that website with
| octave.org ? I thought that historically they were separate because
| you wanted to keep a close watch on the quality of code that got
| labelled as "Octave". I'd like it if all got merged together or was
| more closely and obviously affiliated (think of the questions in the
| user list about people asking for this or that function and apparently
| not aware that it's implemented in Octave-forge).

One problem with merging is licensing.  Octave is part of the GNU
project.  We don't want to host any non-free stuff as part of the
Octave project on savannah.

A similar situation might be autoconf and the autoconf macro archive.
Should all of the contributed macros be hosted as part of the autoconf
project?

Another concern I have is with people contributing code and abandoning
it.  How do the Octave Forge maintainers deal with that problem?  I
know that I don't want to become the default maintainer for all
contributed Octave packages.

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]