Return to gsoc.mdwn CVS log

Up to [NetBSD Developer Wiki] / wikisrc / projects

web commit by spz: adjust the year and "hoping to" instead of "pleased to"

    1: [[!meta title="Google Summer of Code project proposals"]]
    2: 
    3: NetBSD participated successfully in all of Google's Summer of Code
    4: programs to date (see our results of
    5: [2005](http://www.netbsd.org/foundation/press/soc-summary.html),
    6: [2006](http://www.netbsd.org/foundation/press/soc2006-summary.html),
    7: [2007](http://www.netbsd.org/foundation/press/soc2007-summary.html),
    8: [2008](http://www.netbsd.org/foundation/press/soc2008-summary.html),
    9: [2009](http://www.netbsd.org/foundation/press/soc2009.html),
   10: [2010](http://blog.netbsd.org/tnf/entry/google_summer_of_code_2010),
   11: [2011](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of)) and
   12: we hope to once again participate as a mentoring organization in 2013.
   13: 
   14: This page contains a list of concrete suggestions for projects we would
   15: like to see applications for in the next Summer of Code. Note that they
   16: vary a lot in required skills and difficulty. We hope to get applications
   17: with a broad spectrum.
   18: 
   19: In addition, you may wish to discuss your proposal on IRC -- look for us on
   20: Freenodes #netbsd-code or for pkgsrc-related discussions, #pkgsrc. If you
   21: want to just meet the community, visit #netbsd.
   22: 
   23: We encourage you to come up with your own suggestions, if you cannot find a
   24: suitable project here. You can find more project ideas on the
   25: [[NetBSD projects page|projects]]). These are not directly applicable to
   26: Summer-of-Code, but may serve as ideas for your own suggestions. You might
   27: find other ideas in
   28: [src/doc/TODO](http://cvsweb.netbsd.org/bsdweb.cgi/src/doc/TODO?rev=HEAD&content-type=text/x-cvsweb-markup)
   29: and
   30: [pkgsrc/doc/TODO](http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/doc/TODO?rev=HEAD&content-type=text/x-cvsweb-markup).
   31: 
   32: Deadlines and directions for students' applications to the Google
   33: Summer-of-Code can be found
   34: [on the Google pages](http://code.google.com/soc/).
   35: 
   36: # Application process
   37: 
   38: To make the job of sorting out proposals and applications for
   39: NetBSD-related projects, e.g. in the Google Summer-of-Code, easier for us,
   40: there are a few questions that we would like to see answered.
   41: 
   42: If you are interested in working on any of the projects below, please
   43: contact the mailing list referenced on each item, and possibly answer as
   44: many questions from our [[project application guidelines|application]] as
   45: possible.  The interested developers will be glad to respond to you there.
   46: 
   47: **Please note that Google Summer-of-Code projects are a full (day-) time
   48: job.**
   49: 
   50: A positive mid-term evaluation is only possible if usable code has been
   51: committed by that time.  Make sure your schedule allows for this.
   52: 
   53: # Kernel-level projects
   54: 
   55: ## Easy
   56: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:kernel) and tagged(difficulty:easy)"]]
   57: 
   58: ## Medium
   59: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:kernel) and tagged(difficulty:medium)"]]
   60: 
   61: ## Hard
   62: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:kernel) and tagged(difficulty:hard)"]]
   63: 
   64: # Userland projects
   65: 
   66: ## Easy
   67: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:userland) and tagged(difficulty:easy)"]]
   68: 
   69: ## Medium
   70: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:userland) and tagged(difficulty:medium)"]]
   71: 
   72: ## Hard
   73: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:userland) and tagged(difficulty:hard)"]]
   74: 
   75: # pkgsrc projects
   76: 
   77: ## Easy
   78: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:pkgsrc) and tagged(difficulty:easy)"]]
   79: 
   80: ## Medium
   81: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:pkgsrc) and tagged(difficulty:medium)"]]
   82: 
   83: ## Hard
   84: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:pkgsrc) and tagged(difficulty:hard)"]]
   85: 
   86: # Comments
   87: 
   88: We are trying to be fair; expect easy projects to require less knowledge and skill, but quite a bit of work.
   89: 
   90: Medium and hard projects are hard enough to qualify as practical part of a master's thesis (it'll qualify as thesis topic if you can add sufficient quality theoretical parts). We had the honor to mentor several in past GSoCs. Talk to your adviser(s) if and how you can claim academic credit for the project you do with us.
   91: 
   92: We have not yet failed a student who worked hard and actually talked (and listened) to their mentors and the community. If unexpected roadblocks make your project goals too hard to reach in the time given, the goals can be re-negotiated. They will not be for rampant slacking, though.
   93: 
   94: What we expect from contributors (both GSoC students and generally) is that they cooperate, that they are able to communicate (this will mean some English skills, sorry), and that they meet a minimum of good manners towards other people on our lists and other venues. Note that being a specific color, gender, nationality, religion, etc is not listed: If you are willing and able to contribute in a constructive manner, you are welcome.