Re: octave forge fits package

[Olaf Till]

On Thu, Oct 24, 2019 at 08:15:51AM -0400, JohnD wrote:
> > > > -----Original Message-----
> > > > From: Carnë Draug [mailto:address@hidden]
> > > > Sent: Wednesday, January 09, 2019 2:17 PM
> > > > To: JohnD
> > > > Cc: octave-maintainers; Dirk Schmidt
> > > > Subject: Re: octave forge fits package
> > > >
> > > > > > -----Original Message-----
> > > > > > From: JohnD [mailto:address@hidden]
> > > > > > Sent: Friday, January 04, 2019 10:19 AM
> > > > > > To: address@hidden
> > > > > > Cc: address@hidden
> > > > > > Subject: octave forge fits package
> > > > > >
> > > > > > Is anyone actively maintaining this package (or intending to) ?
> > > > > >
> > > > > > Looks like the forge repo hasn't been updated since 2015, and there 
> > > > > > a
> > few
> > > > > > bugs with it so it will now not install in 5.0.1.
> > > > > >
> > > > > > I'll willing to update and make a new release if all are ok with 
> > > > > > that
> > > > > >
> > > > > >
> > > > > > JD
> 
> So what is the protocol external packages that are not maintained? (or 
> maintainer no longer contactable)
> 
> Can I , or someone just take it over and declare it now not an external 
> package? Or create a new package that happens to contain the GPL'd code in it 
> ?
> 
> 

I can't find a 'really external' fits package anywhere, so what we
have at OF seems to be the dead end. I'd say it's ok to take it over.

There seems to be a fits toolbox distributed with Matlab, which is a
reason to maintain fits in the community category of OF, and keeping
the name 'fits'. But then, we should give all the current functions in
our package the names of their Matlab counterparts, and make them
compatible, if possible. OTOH, having the current functions is better
than having no fits package at all. They could be deprecated later in
favour of more Matlab-compatible functions.

Olaf

-- 
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

signature.asc
Description: PGP signature