Stuart Buchanan wrote

> 
> On Wed, Mar 10, 2010 at 12:01 PM, Pete Morgan wrote:
> >
> > Curtis Olson wrote:
> > > One more thing we need.  I need someone to sign up on the google
> > > summer of code page and create an ID for themselves.  The applications
> > > requires a "backup admin" link id and it will not let me enter myself.
> > >
> > > Thanks,
> > >
> > > Curt.
> > Have files this issue
> >
> > #101 - Google Summer Of Code
> >
> > Deasline for mentors = us is Fri 12th at 23:00 UTC.. so everthing needs
> > to be done pretty well a few hours before.. in determingning ideas etc..
> >
> > Its an issue for everyone PLEASE to stick in the ideas NOW.. so they can
> > be reviewed and eliminated..
> >
> > http://code.google.com/p/flightgear-bugs/issues/detail?id=101
> >
> > pete
> 
> Pete,
> 
> This really isn't a bug, is it?
> 
> Having made a great start with putting together a bug tracker, you're
> in real danger of
> ruining it by adding things like this to it.  The bug tracker really
> has to have a focus on
> bugs,  not feature requests, nor random issues.
> 
> As a developer I need a database of the known bugs that I can look over
> easily.
> Having to manually parse out stuff like this is just going to make me
> less likely to
> use it, and therefore make it useless.
> 
> I'd suggest that the wiki is a better place for this sort of information.
> 

Time is of the essence for this issue, if we are not to fail yet again.
While you are quite right, let's not be too picky about this one.

Vivian



------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to