Thinking before posting (or how not to ask for an idea)...
Brad Hards
Consider that GSoC is, in many ways, a job. If you were applying for a job,
would you want your potential employer to know that you couldn't think of
something to apply for? Would you want them to know that you didn't read the
archives before posting?
Alternatively, put yourself in the position of an organisation that is
selecting students. Would you choose a student that had shown that they
understood your project, had maybe used it and sent in some bug reports or
patches, and were committed to the same goals? Or would you choose a student
that showed up saying they had some programming experience in Java (which most
CS students will have) but otherwise seemed pretty unaware of what would be
required?
If you want to get selected, do your research first.
Brad
Dirk Haun
> Would you want them to know that you didn't read the
> archives before posting?
Of course, the students asking these questions aren't reading the
archives (obviously) and therefore won't see your post either ;-)
I agree with everything you wrote, but we should keep in mind that
GSoC is probably the first time many of these students are using
things like mailing lists. So we should accept the fact that they may
not be familiar with mailing list etiquette, for example
(incidentally, this is one of the items mentioned on the GSoC flyer).
Matthew Wilkes
On 2010-02-28, at 0417, Brad Hards wrote:
> If you want to get selected, do your research first.
^^^ This.
They may not search the archives when choosing projects, but I search
them when choosing students.
Matt
joel.s...@gmail.com
On Feb 27, 10:17 pm, Brad Hards <br...@frogmouth.net> wrote:
> For potential students, a thought from a potential mentor / admin:
>
> Consider that GSoC is, in many ways, a job. If you were applying for a job,
> would you want your potential employer to know that you couldn't think of
> something to apply for? Would you want them to know that you didn't read the
> archives before posting?
I think it is important to iterate that the student should treat this
like a summer job.
It is the roughly the same amount of money my daughter made as a
summer intern
at a biotech research institute. She was working ~30 hours a week
during her
summer break and got paid by the hour. You do the math. :)
Also we ask our students to set their own mid-term and final
deliverables. They
specifically tell us what they want their success to be measured by.
This saves
us some heartburn when evaluating students and makes expectations
clear.
>
> Alternatively, put yourself in the position of an organisation that is
> selecting students. Would you choose a student that had shown that they
> understood your project, had maybe used it and sent in some bug reports or
> patches, and were committed to the same goals? Or would you choose a student
> that showed up saying they had some programming experience in Java (which most
> CS students will have) but otherwise seemed pretty unaware of what would be
> required?
>
> If you want to get selected, do your research first.
Our best students have been proactive. They were helping other
students get
up to speed. Not only did they do their own prep work, they had the
open source
spirit and helped others.
--joel sherrill
RTEMS
> Brad
Rohan Prabhu
--
You received this message because you are subscribed to the Google Groups "Google Summer of Code Discuss" group.
To post to this group, send email to google-summer-...@googlegroups.com.
To unsubscribe from this group, send email to google-summer-of-cod...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-summer-of-code-discuss?hl=en.
Shashank Todwal
archives, how can we expect him to work for the prestigeous gsoc.
I see so many redundant posts that now its very hard to find the important ones
> --
> You received this message because you are subscribed to the Google Groups
> "Google Summer of Code Discuss" group.
> To post to this group, send email to
> google-summer-...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-summer-of-cod...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-summer-of-code-discuss?hl=en.
>
>
--
Sent from my mobile device
magnifi...@gmail.com
every student has to show his innovations which are nothing but the
project ideas of his own
Thiago Macieira
I don't know about other projects, but at least in KDE we have had no shortage
of students who have read the mailing lists and do know what to apply.
So , this is something else for students to think of: they are competing with
these other students. Even if they don't read this email and find it out.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
Sarma Tangirala
--
You received this message because you are subscribed to the Google Groups "Google Summer of Code Discuss" group.
To post to this group, send email to google-summer-...@googlegroups.com.
To unsubscribe from this group, send email to google-summer-of-cod...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-summer-of-code-discuss?hl=en.
--
Regards,
Sarma Tangirala, tvssarm...@gmail.com