Next steps and what to do during the bonding period

[Jonathan Leto]

Howdy students!

I would like to congratulate all the students who were accepted this
year [0] as well as say to students who were not accepted:

1) Stick with it. Learning from the students this year is one of the
best ways to get accepted next year.
2) Some proposals would be great for TPF grants, so don't just throw
them away! Keep at it.
3) If you really believe in the importance of your project, do it
anyway. Don't let not getting into GSoC stop you.

As for the accepted students, I realize that many of you are taking
finals and things, but you should be thinking of how to be most
effective this year, setting up your environment and making sure that
you know how to use all the tools that will be needed to succeed this
summer. All GSoC students have mandatory homework of 1 *high quality*
blog post per week, as well as *at least 1 blog post* during the
bonding period to prove that you have your blog setup working. "High
quality" means you provide actual details, links to the things you are
talking about and show the community that you are serious about your
project. Not submitting your weekly blog post (as well as 1 during the
bonding period) could cause you to be failed at mid-terms, so please
take this seriously. I will not give a "at least 3 paragraphs"
stipulation or somesuch other arbitrary rule. You will know if your
blog post is high quality or not, and so will your peers. It is best
to err on the side of too much quality, rather than not enough.

For students under the Parrot Foundation, you will be posting to the
parrot.org website, so part of your bonding period homework is getting
a login to the site and making sure it works. Figuring out how to do
that will force you to interact with the community, so go hang out in
#parrot or ask on parrot-dev :) Parrot students also have the
additional homework of attending the weekly #parrotsketch IRC meeting.
If you can't make the time, you can just paste a short status report,
which can be a summary of your blog post or a rough draft of it. To
see what the status reports look like, there are logs.

For students under The Perl Foundation, you will either have to setup
a blog account with your communities blog or setup your own. Please
let me know if your community does not have a blog or if you need help
setting up your own.

Again, congratulations to everyone, more information will follow. If
there are any questions, please ask them on this list so that all
students benefit from the answer.

Duke


[0] - http://news.perlfoundation.org/2010/04/google-summer-of-code-accepted.html
[1
--
Jonathan "Duke" Leto
jona...@leto.net
http://leto.net

--
You received this message because you are subscribed to the Google Groups "tpf-gsoc-students" group.
To post to this group, send email to tpf-gsoc...@googlegroups.com.
To unsubscribe from this group, send email to tpf-gsoc-stude...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tpf-gsoc-students?hl=en.

[Jonathan Leto]

Howdy,

More stuff:

1) tell your mentors about your blog, and submit it to blog
aggregators, such as perlsphere/planet parrot/ironman etc

2) the student should insist on weekly status meetings, even if the
mentor doesn't deem them important. If your mentor seems aloof, let me
know.

Also, the link for the IRC logs in the previous email is:

http://irclog.perlgeek.de/

Duke