octave-maintainers
[Top][All Lists]
Advanced

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

Re: Working on nnet package


From: Julien Bect
Subject: Re: Working on nnet package
Date: Mon, 2 Jan 2017 22:33:20 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0

Le 02/01/2017 à 21:50, c. a écrit :
On 1 Jan 2017, at 19:25, Nir Krakauer <address@hidden> wrote:
Hi Francesco,

I agree with your approach. Matlab's Neural Network Toolbox is fairly widely 
used. It would be a good thing to have a drop-in replacement in Octave. I 
suggest that once you are happy with a set of your changes, you can post a 
notice to the patch tracker and someone can review it for pushing to the Forge 
repository.
I don't think this is a viable approach.

The nnet package is currently unmaintained, so probably nobody cares and nor
understands the existing code. It is very unlikely that anyone will ever take
the time to review Francesco's changes.

Francesco has already proven his skills and commitment while working on GSoC, so
I would suggest instead to mark Francesco as the new maintainer of nnet and let
him do the changes directly.

Carlo,

I don't think there is such a thing as "mark[ing] Francesco as the new maintainer"... as long as the package is considered unmaintained ;-)

Joking aside: I agree with you that Francesco should be given dev permissions if he is interested in working on nnet (since, as you said, it is very unlikely that someone will want to review his patches).

But I don't know who could do this right now ...

Any OF admin can do it, I think, but... Who are the admins of the OF project, presently?

@++
Julien




reply via email to

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