Having no clear opinion on this, I do have a comment (see below:)
Lukas Reichlin wrote:
> I think we should group OF packages into different classes as the
> long list on
> http://octave.sourceforge.net/packages.php is rather confusing. For
> example, we could use three classes:
>
> - main: only a
On 24 April 2012 13:57, Carlo de Falco wrote:
> 2012/4/24 Lukas Reichlin
>>
>> I think we should group OF packages into different classes as the
>> long list on
>> http://octave.sourceforge.net/packages.php is rather confusing. For
>> example, we could use three classes:
>>
>> - main: only about
2012/4/24 Lukas Reichlin
> I think we should group OF packages into different classes as the
> long list on
> http://octave.sourceforge.net/packages.php is rather confusing. For
> example, we could use three classes:
>
> - main: only about a dozen of packages. The most popular ones, of
> general
On Tue, Apr 24, 2012 at 12:36 PM, Lukas Reichlin
wrote:
> I think we should group OF packages into different classes as the
> long list on
> http://octave.sourceforge.net/packages.php is rather confusing. For
> example, we could use three classes:
>
> - main: only about a dozen of packages. The mo
I think we should group OF packages into different classes as the
long list on
http://octave.sourceforge.net/packages.php is rather confusing. For
example, we could use three classes:
- main: only about a dozen of packages. The most popular ones, of
general use. High quality. Tested and actively
d
