--- wikisrc/projects/application.mdwn 2011/11/06 20:15:10 1.1
+++ wikisrc/projects/application.mdwn 2011/11/25 21:49:29 1.2
@@ -1,25 +1,28 @@
-[[!meta title="How to apply for a project"]]
+[[!meta title="Guidelines to apply for a project"]]
-To make the job of sorting out proposals and applications for
-NetBSD-related projects, e.g. in the Google Summer-of-Code, easier for us,
-there are a few questions that we would like to see answered in your
-project application, as outlined below.
-
-Deadlines and directions for students' applications to the Google
-Summer-of-Code can be found
-[on the Google pages](http://code.google.com/soc/).
-
-A listing of possible NetBSD Summer-of-Code project suggestions can be
-found [[on the NetBSD Summer-of-Code page|projects/gsoc]]. We encourage
-you to come up with your own suggestions, if you can not find a suitable
-project there. You can find more project ideas
-[[on the NetBSD project ideas page|projects]]. These are not directly
-applicable to Summer-of-Code, but may serve as ideas for your own
-suggestions.
+If you plan to apply to work on any of the projects listed in this site,
+you should start by sending an email to the contact points listed at the
+top of every project description. The purpose of this email is to
+introduce yourself to the NetBSD community if you are new to it, and to
+explain in a great level of detail how you will work on the project
+(e.g. the overall plan, milestones, schedule, etc.) **This is particularly
+important if the project is up for funding or if it is a
+[[Google Summer of Code project|gsoc]].**
+
+The sections below include a guideline on the kind of information we are
+interested in hearing in your initial communication. The level of detail
+involved will depend on how how familiar you are with the NetBSD Project
+and the developer community.
+
+If you are a newcomer (e.g. you are a Google Summer of Code student that
+has just installed NetBSD for the first time), you are encouraged to answer
+as many questions as possible. If you are an old-timer, however, you can
+skip the most obvious questions and focus on preparing a detailed project
+specification instead.
# About your project
-* What is the goal of the project? (Short overview)
+* What is the goal of the project? (Short overview)
* What will be the deliverables of the project? (Code, documentation, ...)
@@ -79,15 +82,7 @@ suggestions.
either the names/email addresses of those developers or point us towards
the discussions on our list (via ).
-* How do we contact you for question, comments, suggestions etc?
+* How do we contact you for question, comments, suggestions, etc.?
* Is there anything else you'd like us to know? Did we forget any important
details or questions?
-
-# Caveats
-
-* Please note that Google Summer-of-Code projects are a full (day-) time
- job.
-
-* A positive mid-term evaluation is only possible if usable code has been
- committed by that time. Make sure your schedule allows for this.