[gentoo-soc] Final Gentoo GSOC proposal requirements

[gentoo-soc] Final Gentoo GSOC proposal requirements

[Brian Dolbec]

Thank you all for your proposals.  This is a reminder to all students.

There are some of you that have not yet met all our requirements.

We need to set a hard deadline of 12:00 noon UTC, Wednesday, April 12,
for all Gentoo proposal requirements to be met.  We will then be making
our final decisions and subsequent submission to Google.  No one will
know the final results until Google makes their announcement and posts
the results of the accepted students.
See the GSOC timeline for that information.


Gentoo specific requirements include:

1) Joining the gentoo-soc email list, sending an email introducing
yourself and your proposal idea (not the detailed proposal).

2) Making yourself available now for questions, etc. in our #gentoo-soc
IRC channel.  While reviewing your proposals, we may have questions and
ask you to clarify or expand on something from your proposal.

3) Fixing at least one bug, preferably in a related package with
a similar/same VCS.  Attaching patches to the bug and/or making a pull
request to the appropriate gentoo repo for review/merge. 
AKA, we want to see some proof that you can work with the code, VCS and
our own bugzilla.  It may not always be possible to have bugs directly
relating to your proposal.  In that case please contact us so we may
suggest some bugs.

4) If any of the potential mentors has asked anything of you to further
your proposal, clarify, etc..., please ensure you make every effort to
accomplish and provide that.  If not by direct email or IRC to that
mentor, then at least to this email list so it is view-able by all
project mentors & reviewers.

Remember, the sooner you meet all these requirements, the better may
be your chances of being accepted.  Communication between students and
mentors is a key factor to a successful GSOC project.  So, your
communication between mentors and yourself is also part of our decision
process.

Thank you,
Gentoo Summer of Code team
-- 
Brian Dolbec <dolsen>