path: root/community/gsoc.mdwn
diff options
authorThomas Schwinge <>2014-03-16 16:36:08 +0100
committerThomas Schwinge <>2014-03-16 16:36:08 +0100
commit9315421090088924c66a8f6e97ee3e0105d17617 (patch)
tree5a3a2e12559e308cefcf6fccce7b65a5eb297ab5 /community/gsoc.mdwn
parent0ce632f1ef115b00ffb059eb74a97252aefa4025 (diff)
GSoC 2014.
Diffstat (limited to 'community/gsoc.mdwn')
1 files changed, 10 insertions, 10 deletions
diff --git a/community/gsoc.mdwn b/community/gsoc.mdwn
index e6f0782..5a37301 100644
--- a/community/gsoc.mdwn
+++ b/community/gsoc.mdwn
@@ -1,5 +1,5 @@
-[[!meta copyright="Copyright © 2008, 2009, 2010, 2011, 2012, 2013 Free Software
-Foundation, Inc."]]
+[[!meta copyright="Copyright © 2008, 2009, 2010, 2011, 2012, 2013, 2014 Free
+Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -11,24 +11,28 @@ License|/fdl]]."]]"""]]
[[!meta title="Google Summer of Code"]]
The Google Summer of Code 2013 is over. Chances are that we will again be
participating in 2014, stay tuned.
We're in! The GNU Hurd project is again participating in the [Google Summer of
Code]( under the [GNU
-As of Monday, 2013-04-22 it's the *student application period*. This will last
-until [Friday,
-2013-05-03](, which
+Per the [Google Summer of Code 2014 Program
+Timeline](, on
+Monday, from 2014-03-10 to 2014-03-21, it's the *student application period*,
is plenty of time for preparing and discussing your applications -- but please
don't wait to the last minute!
This year's *student application period* is over. Thanks for sending in your
applications! We're now reviewing and discussing these, so please pay
attention to any questions posted on your proposal's page. The Google site's
notification system should be sending out emails, too.
As we only have finite resources (meaning that we won't be able to accept all
GNU Hurd applications even if we wanted to), we will eventually need to make a
@@ -37,7 +41,6 @@ with us, be it by answering the evaluators' questions on your proposal's page,
or by talking to us on the [[mailing_lists]] or on [[IRC]]. At this time, it
is important for us to get a good impression about the seriousness you're
showing with your application.
If you intend to apply for any such projects in the future, it's a good idea to
already start perparing for it now: the sooner, the better.
@@ -47,14 +50,12 @@ send in some basic patches (as mentioned in our
[[student_application_form]]), and talk to us on the [[mailing_lists]] or
on [[IRC]], for example about the principal steps you're
planning on doing in your intended work area.
Of course, we don't expect you
to already start working seriously on your project, but any input you're giving
us will make it easier for us to justify selectiong your specific proposal. At
this time, it is not quantity that matters, and it also is not *the perfect
patch* we're waiting for, but it is rather that we see how you're generally
able to work with the code.
If you have any questions, don't be shy: please ask! Nobody expects you to
know everything. Even for the long-term Hurd contributors it is common to
@@ -73,7 +74,6 @@ discussing with our GNU peers about how to split these up among all the GNU
# Possible projects
We have a list of [[project_ideas]], and students are likewise encouraged to