[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Savannah-hackers] [gnu.org #212478] where to send project for evalu
From: |
Sylvain Beucler via RT |
Subject: |
Re: [Savannah-hackers] [gnu.org #212478] where to send project for evaluation? |
Date: |
Sat, 16 Oct 2004 13:25:40 -0400 |
Hi,
On second though, I think I have a more precise question: should we do
any preprocessing in the GNU Evaluation process (aside from the
Savannah evaluation itself)? I mean, determining whether to send a
project to you is a form of "preprocessing".
So:
- either we do not forward you project without code; this will not
take us long to add a note when approving the project, but we may
act differenly than you would
- either we forward you any project wanting to be GNU (as long as it
is approved at Savannah) without trying to see if it is worth doing
so; you'll take care of telling them whether you need code or not
What do you prefer?
--
Sylvain
On Sat, Oct 16, 2004 at 01:02:01PM -0400, Karl Berry via RT wrote:
> Hi Sylvain and all,
>
> Although the eval team has a procedure for helping authors with software
> in early stages, I'm not sure if such a package could actually be
> officially dubbed. We'd have to ask rms for a definitive answer, if
> it's important. My personal view is that it would be pretty meaningless
> to dub something GNU before it is written -- that could lead to GNU
> vaporware. Coming up with big and brilliant plans is (usually) not the
> hard part.
>
> On the other hand, if there is a reasonable amount of code, even if it
> is not releasable or even necessarily compilable, then that can be
> enough (though certainly not ideal). For example, that oxygen package
> you just sent through mentioned a url to the source, so I figure he's
> somewhat further along than just planning.
>
> Does that help?
>
> Best,