On Wed, Feb 15, 2012 at 2:58 PM, Noy <[email protected]> wrote:

> The other option is to basically offer a set list of projects to work on.
> Frankly I think that should be the way to go, because the problems were
> identified as far back as 2010. I think the problem is that alot of GSOC
> candidates come to the program with very little experience about what is
> required and needed. so they offer ideas that might seem new and useful,
> but actually won't be in the long run. Having directed projects really
> allows the developers to play a stronger conceptual role in ensuring that a
> contribution is useful for the project. We would get less "dead" programing
> in the long term.
>

I tend to agree with this, and in particular think that we should focus on
very very small projects with unambitious sounding goals -- and then ask
the students to do a thorough job of them.

Aggressive GSoC projects just don't work very well.

David
_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev

Reply via email to