Re: [Savannah-hackers-public] requirements of a new project in GNU Savannah

[Ineiev]

Hello, Assaf;

On 08/12/2014 10:08 PM, Assaf Gordon wrote:
> While reviewing a recent project submission, I commented that I couldn't 
> get the project to build because I'm not sure what are the required 
> packages.
>
> Karl commented:
> On 08/12/2014 05:22 PM, Karl Berry wrote:
> > In general, it's not necessary that a package compile, let alone
> > work, to be enabled on savannah.
> >
> > The crucial thing is, as I guess you know, that the dependencies all
> > be free software.
>
>
> To which I replied:
> <... snip... >
> > As a general policy, with so many other possibilities for the
> > general public to host their software elsewhere, wouldn't GNU
> > Savannah prefer to raise the bar and hosts projects that at least
> > preset some level of useability?
> >
> > With the administration resources already [spread] so thin, adding a
> > new 'ghost' project that doesn't work or compile doesn't really "add
> > value" to free software...
> >  Wouldn't you want to encourage good projects and discourage bad ones?
> > let other services host those  projects...

Just a datapoint:

I think freedom is the most important quality; if a package is free,
it's generally good [0].

In particular, my only real package submission [1] may have been (barely)
functional, but it wasn't very simple to build (it needed a cross-compiler),
and even harder to test (it run on a custom board). I'm not sure whether
it would pass the prospective criterion, but there is no doubt it was
very important for me, personally.

[0] 
https://www.gnu.org/philosophy/when_free_software_isnt_practically_better.html
[1] https://savannah.gnu.org/task/index.php?5161