torproject/webwml
1
0
Fork 0
mirror of https://github.com/torproject/webwml.git synced 2024-12-12 12:36:38 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updating GSoC page for 2012 and rewriting some sections

Browse Source 
Changing the dates and linking to the 2012 GSoC page. Some of the sections were
kinda rough or gave out of date advice so this includes quite a bit of
rewording too.
This commit is contained in:
Damian Johnson 2012-02-25 19:58:43 +00:00
parent c16bf8c3cc
commit 2d8e24bc74
1 changed files with 57 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

104
about/en/gsoc.wml
View File

@ -9,28 +9,29 @@
<a href="<page about/gsoc>">Google Summer of Code</a>
</div>
<div id="maincol">
<h2>Tor: Google Summer of Code 2011</h2>
<h2>Tor: Google Summer of Code 2012</h2>
<hr>
<p>
In the last four years, The Tor Project in collaboration with <a
In the last five years, The Tor Project in collaboration with <a
href="https://www.eff.org/">The Electronic Frontier Foundation</a>
successfully took part in
<a href="http://code.google.com/soc/2007/eff/about.html">Google Summer of Code
2007</a>, <a href="http://code.google.com/soc/2008/eff/about.html">2008</a>,
<a
href="http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/eff">2009</a>,
and <a href="<blog>tor-google-summer-code-2010">2010</a>.
In total we had 21 students as full-time developers for the summers of 2007 to
2010. Now we are applying to <a
href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2011">Google
Summer of Code 2011</a>.
<a href="<blog>tor-google-summer-code-2010">2010</a>, and <a
href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2011">2011</a>.
In total we had 27 students as full-time developers for the summers of 2007 to
2011. Now we are applying to <a
href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2012">Google
Summer of Code 2012</a>.
</p>
<p>
The <a
href="https://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline">timeline</a>
for GSoC 2011 is available.
href="https://google-melange.appspot.com/gsoc/events/google/gsoc2012">timeline</a>
for GSoC 2012 is available.
</p>
<p>
@ -64,11 +65,11 @@
<h2><a class="anchor" href="#GettingInvolved">How To Get Involved</a></h2>
<p>
The best way to get involved is to come listen on IRC (both "#tor" and
"#tor-dev"), read our docs and other webpages, try out the various tools
that are related to the projects that interest you, and ask questions
as they come to you: <a href="<page docs/documentation>#UpToSpeed">Getting
up to speed</a>.
The best way to get involved is to come <a href="<page
about/contact>#irc">listen on IRC</a> (both "#tor" and "#tor-dev"), read
our docs and other webpages, try out the various tools that are related to
the projects that interest you, and ask questions as they come to you: <a
href="<page docs/documentation>#UpToSpeed">Getting up to speed</a>.
</p>
<p>
@ -84,7 +85,7 @@
<p>
When it comes time for us to choose projects, our impression of how well
you'll fit into our community &mdash; and how good you are at taking
you'll fit into our community &mdash; and how well you are at taking
the initiative to do things &mdash; will be at least as important as
the actual project you'll be working on.
</p>
@ -99,19 +100,20 @@
</p>
<p>
The best kind of ideas are A) ones that we know we need done real soon
now (you can get a sense of urgency from the priority on the wishlist,
and from talking to the potential mentors), and B) ones where it's
clear what needs to be done, at least for the first few steps. Lots of
students try to bite off open-ended research topics; but if you're going
to be spending the first half of your summer figuring out what exactly
you should code, and there's a chance that the conclusion will be "oh,
that isn't actually a good idea to build", then your proposal will make
us very nervous. Try to figure out how much you can actually fit in a
summer, break the work down into manageable pieces, and most importantly,
figure out how to make sure your incremental milestones are actually
useful &mdash; if you don't finish everything in your plan, we want to
know that you'll still have produced something useful.
The best kind of ideas are well defined and easily broken into subtasks.
A lot of students try to bite off open-ended development and research
topics. But if you're going to spend the first half of your summer figuring
out what exactly you should code, there's a chance that the conclusion will
be "oh, that isn't actually feasible to build after all" and your proposal
will make us very nervous.
</p>
<p>
Try to figure out how much you can actually fit in a summer, break the work
down into manageable pieces, and most importantly, figure out how to make
sure your incremental milestones are actually useful &mdash; if you don't
finish everything in your plan, we want to know that you'll still have
produced something useful.
</p>
<a id="Template"></a>
@ -171,37 +173,45 @@
helps with the deduplication process and will not impact if we accept your
application or not.</li>
<li>Is there anything else we should know that will make us like your
<li>Is there anything else that we should know that will make us like your
project more?</li>
</ol>
<p>
We will pick out mentors for this year &mdash; most of the
people on the <a href="<page about/corepeople>">core Tor development team</a>
plus a few people from <a href="http://www.eff.org/about/staff">EFF's staff</a>
&mdash; so we should be able to accommodate a wide variety of projects,
ranging from work on Tor itself to work on supporting or peripheral
projects. We can figure out which mentor is appropriate while we're
discussing the project you have in mind. We plan to assign a primary
mentor to each student, along with one or two assistant mentors to help
answer questions and help you integrate with the broader Tor community.
We mostly pick mentors from the <a href="<page about/corepeople>">core Tor
development team</a> and <a href="http://www.eff.org/about/staff">EFF's
staff</a> so we should be able to accommodate a wide variety of projects.
These can range from work on Tor itself to work on supporting or peripheral
projects.
</p>
<p>
All selected projects are assigned both a primary and assistant mentor to
answer your questions and help you integrate with the broader Tor
community. Though your mentors are a primary point of contact please use
our public spaces (the <a href="<page about/contact>#irc">#tor-dev irc
channel</a> and <a href="<page docs/documentation>#MailingLists">tor-dev@
email list</a>) to discuss your project. We want you to become a part of
the community by the end of the summer, not a stranger that's only known by
your mentor.
</p>
<p>
If you're interested, you can either contact the <a href="<page
about/contact>">tor-assistants list</a> with a brief summary of your proposal
and we'll give you feedback, or just jump right in and post your ideas
and goals to the <a href="<page docs/documentation>#MailingLists">tor-talk
mailing list</a>. Make sure to be responsive during the application
selection period; if we like your application but you never answer our
mails asking for more information, that's not a good sign.
about/contact>">tor-assistants list</a> (a private list) with a brief
summary of your proposal and we'll give you feedback, or just jump right in
and post your ideas and goals to the <a href="<page
docs/documentation>#MailingLists">tor-dev mailing list</a> (which is open).
Make sure to be responsive during the application selection period; if we
like your application but you never answer our mails asking for more
information, that's not a good sign.
</p>
<p>
The more applications we get, the more likely Google is to give us good
students. So if you haven't filled up your summer plans yet, please
consider spending some time working with us to make Tor better!
We're always happy to have new contributors so if you haven't filled up
your summer plans yet, please consider spending some time working with us
to make Tor better!
</p>
<a id="Example"></a>