On 15-Feb-12, at 12:24 PM, Ignacio Riquelme Morelle wrote:
ature to maintain.
In my opinion, these two particular points are only relevant for
huge and
intrusive projects like the Whiteboard (which as I recall, was
started as part
of GSoC 2010 and continued in the same program in 2011), or projects
outside
our general area of expertise (UMC Editor, which fortunately
continues to be
maintained by timotei).
Of course, it's hard to give an opinion on whether these concerns
apply or not
for a particular case without a preliminary projects proposal to
work with.
--
Regards
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.
Under such a scheme, we would not take unsolicited proposals.
Potential projects should be defined by the mentors, and projected to
be reasonably accomplishable during GSOC's term. The actual scope
would be reasonably well sketched out beforehand, and should not be
something too ambitious in terms of work or design. While this might
be more work for the developer at the start, I think it will improve
outcomes and reduce the actual burden in the long term. You'd have a
set problem that different candidates can be evaluated by, and there
would be less surprises for the student who wins. The creativity of
the candidate would show through on the implementation.
While this might seem a bit draconian, I think its deals with most of
the problems outlined in Mordante's email. I think keeping students in
the program is difficult regardless, but it should reduce the other
negative effects that has been highlighted. Students will still get a
sense of the open source atmosphere and have a meaningful work
experience coding for the summer.
As for the admin side, I think the workload between Ivanovic and I
worked fairly well, and unless he says otherwise we might go with
that. I'll be around the help screen potential candidates too.
_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev
