[[!meta title="How 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
# About your project
* What is the goal of the project? (Short overview)
* What will be the deliverables of the project? (Code, documentation, ...)
* Give an overview of how you intend to reach the project's goal
in the form of milestones and a schedule.
* Is similar software already available elsewhere, e.g. for
Linux or any other BSD?
* Is the project a port of software, or a rewrite? (remember:
No GPL in the NetBSD kernel!)
# About your project and NetBSD
* If your working area is the core NetBSD operating system: have you
installed NetBSD and made first experiences with hands-on configuration?
Have you rebuilt the kernel and the userland, either in full or in parts?
If you plan to work on pkgsrc, have you installed packages from source
and binary? Have you created a package on your own?
* Have you found the relevant places that your project is based on in the
source code, and read through it?
* How will your project integrate into NetBSD? (Userland tool, kernel
subsystem, driver, patch set, pkgsrc, ...)
* What interfaces in NetBSD will your project use? (Go into details here!
What module/file names, functions, data structures etc. are of relevance
for your project?)
* To what degree are you familiar with those interfaces? (not/some/very,
* Is knowledge on other topics required for this project, e.g. on
hardware, software other than NetBSD, APIs, protocols, etc.? If so, give
details and references.
* To what degree are you familiar with those? (not/some/very, details?)
* If the project involves hardware (e.g. writing drivers, doing a port to
new hardware, ...): do you own the hardware or have access to?
# About you
* Can you list some prior projects that you have worked on so far? Include
details like programming language, duration, number of people involved,
project goal, if you used CVS, SVN or similar, and whatever else we may
find thrilling! If you have a CV/resume online, feel free to include a
* Do you have any prior experience with programming NetBSD? In what area?
If you did send some problem reports (PRs) or patches, please include
* Have you previously discussed your project within NetBSD, either on a
mailing list or with some specific developers? If so, please give us
either the names/email addresses of those developers or point us towards
the discussions on our list (via <http://mail-index.NetBSD.org/>).
* 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?
* Please note that Google Summer-of-Code projects are a full (day-) time
* A positive mid-term evaluation is only possible if usable code has been
committed by that time. Make sure your schedule allows for this.
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb