[Top][All Lists]

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

Re: bioinfo package - maintenance of ...

From: Alois Schloegl
Subject: Re: bioinfo package - maintenance of ...
Date: Sat, 30 Dec 2017 16:43:45 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2

On 2017-12-29 11:22, Olaf Till wrote:
> Alois,
> Oliver and me currently consider to ask the maintainers to vote on
> turning 'bioinfo' into an 'external' Octave Forge package


do I need to wait until this vote has happened ? If yes, when will this
vote take place? (Out of curiosity - who is eligible to vote ?)

> https://octave.sourceforge.io/dev-descr-two-groups.php
> despite the fact that it corresponds to a Matlab toolbox.

I'm not sure I understand; what difference does it make whether it
corresponds to a Matlab toolbox ?

> But once someone else should be willing and able to maintain it in the
> 'community' group again, and we see a need for it, we would let him do
> so, and therefore take the corresponding 'external' package off again
> from Octave Forge.

I'm not sure I understand; what do you mean by "[taking a] .. package
off .. Octave Forge" ? And even a "community" package is usually
maintained on Octave Forge - why would you take it off ? Do I need to
worry about this - or is this about some other unrelated issue ?

> Would you accept this?
> Olaf

The two links
do not contain any language about requiring a specific (i.e.
octave-only) coding style. This is good and addresses my main concern.
This will allow maintaining compatibility to both target platforms,
Matlab and Octave, and no code-duplication would be necessary.

In summary, yes, this seems more than acceptable to me, Actually, if I
understand this correctly, it's not only "acceptable" but matches the
desired solution.


reply via email to

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