Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Re: Some random gsoc2008 thoughts

Re: Some random gsoc2008 thoughts

From: Austin Appel <scorche15_at_gmail.com>
Date: Wed, 19 Mar 2008 22:34:45 -0700

Daniel Stenberg wrote:
> A. Weekly Reports
>
> We should insist on getting weekly, public, reports on what happens.
> We should push the students somewhat harder this year to be more
> public from the start since there's rarely much reason to keep things
> private between the mentor and student only (of course some stuff will
> and should still be private). The sooner the work and code gets seen,
> reviewed and commented by the larger community the better. Of course
> weekly reports would also be used to track the progress and to allow
> everyone else to see how they can assist, should help be needed.
I do think weekly reports would be a good amount, as hopefully, this
year they will be joining us in IRC and talking there as well. If they
are not in IRC (which I would like to mandate this year, although there
can be circumstances which I would allow otherwise), then yes I think we
could ask for more frequent updates.
> C. Questions
>
> When answering these questions, please try to explain as good as
> possible and "sell yourself" as we might use the answers you provide
> as basis for selecting whom to accept as students. Your answers will
> not become public, but will be read by Rockbox committers/gsoc mentors.
>
Might want to add a sentence or 2 about not worrying if you lack in
certain areas/don't have examples/resume and just to be truthful. As
well, I certainly wouldn't mind having them come into IRC when they
submit their proposal.
> 2. Have you built Rockbox yourself from source before?
I might even want to add an "If not, please set up a compiling
environment (have a link to the #For_Developers section of the index)
and come back when you have done so successfully.
>
> 3. What programming experience do you have, and in which languages? If
> those
> don't include C, please tell us how you intend to deal with this lack.
> 4. What open source experiences do you have?
Perhaps add a bit to see if they have any sample code lying around.

Also, I wouldn't mind asking to see if they have any sort of resume they
can link to, any blogs, a few questions about how capable they are to
come on IRC all/most of the time, how well suited to the project at hand
they feel they are, where they live and go to school, how they heard of
Rockbox, what other projects they may be submitting for, etc.

I am not sure how much of this should be on the actual proposal and how
much can be in live IRC conversation though.
Received on 2008-03-20


Page was last modified "Jan 10 2012" The Rockbox Crew
aaa