|author||Thomas Schwinge <email@example.com>||2011-04-09 21:18:38 +0200|
|committer||Thomas Schwinge <firstname.lastname@example.org>||2011-04-09 21:18:38 +0200|
Diffstat (limited to 'community/gsoc.mdwn')
1 files changed, 48 insertions, 12 deletions
diff --git a/community/gsoc.mdwn b/community/gsoc.mdwn
index 73a69b8..c7d0ec5 100644
@@ -11,20 +11,51 @@ License|/fdl]]."]]"""]]
[[!meta title="Google Summer of Code"]]
-We're in! The GNU Hurd project will again participate in the [Google Summer of
+We're in! The GNU Hurd project is again participating in the [Google Summer of
Code](http://www.google-melange.com/gsoc/homepage/google/gsoc2011) under the
-As of Monday, 2011-03-28 it's the *student application period*. This will last
-is plenty of time for preparing and discussing your applications -- but please
-don't wait to the last minute!
-## Applying for a Task
+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
+choice about whom to select. For this, it is a very good idea to be in contact
+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.
+It is a good idea to get familiar with the GNU Hurd, by reading some of our
+[[documentation]], and by using a GNU/Hurd system. It is also a good idea to
+send in some basic patches (this has already been mentioned in our
+[[student_application_form]]), or discuss with us some principle 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 what 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
+openly post messages to [[mailing_lists/bug-hurd]] saying: *Hey, I don't know
+how to do `X`, can someone please help me?* And, as we're not working next to
+each other in a conventional office or university setup, we'll need to
+establish and get used to different communication channels.
+boring as it is, but the next step is waiting: we will have to wait for Google
+to announce the number of slots that the whole GNU project gets, and we'll be
+discussing with our GNU peers about how to split these up among all the GNU
+# Applying for a Task
+Applications for 2011 are closed.
We have a list of [[project_ideas]], and students are likewise encouraged to
submit their own project proposals.
@@ -40,8 +71,13 @@ Please read up about [[contributing]] in general;
and feel free to ask any questions you might have at one of our [[regular_IRC_meetings|IRC#regular_meetings]].
Generally it's a good idea to [[contact_us|communication]] when starting to work on some project.
+## Outside of the GSoC Scope
Working on one of these projects is generally a good opportunity to get started
-with Hurd development, even outside of the GSoC context.
+with Hurd development, even outside of the GSoC context. Please don't hesitate
+to contact us regarding mentoring even if it's not GSoC time at the moment, or
+if you aren't a student anyway.