Return to gsoc.mdwn CVS log

Up to [NetBSD Developer Wiki] / wikisrc / projects

web commit by mspo

    1: [[!meta title="Google Summer of Code project proposals"]]
    2: 
    3: NetBSD participated successfully in all of Google's Summer of Code
    4: programs up to 2013 (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),
   12: [2012](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of1),
   13: [2013](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of2)) and
   14: we are hoping to once again participate as a mentoring organization in 2015.
   15: 
   16: This page contains a list of concrete suggestions for projects we would
   17: like to see applications for in the next Summer of Code. Note that they
   18: vary a lot in required skills and difficulty. We hope to get applications
   19: with a broad spectrum.
   20: 
   21: In addition, you may wish to discuss your proposal on IRC -- look for us on
   22: Freenodes #netbsd-code or for pkgsrc-related discussions, #pkgsrc. If you
   23: want to just meet the community, visit #netbsd.
   24: 
   25: We encourage you to come up with your own suggestions, if you cannot find a
   26: suitable project here. You can find more project ideas on the
   27: [[NetBSD projects page|projects]]). These are not directly applicable to
   28: Summer-of-Code, but may serve as ideas for your own suggestions. You might
   29: find other ideas in
   30: [src/doc/TODO](http://cvsweb.netbsd.org/bsdweb.cgi/src/doc/TODO?rev=HEAD&content-type=text/x-cvsweb-markup)
   31: and
   32: [pkgsrc/doc/TODO](http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/doc/TODO?rev=HEAD&content-type=text/x-cvsweb-markup).
   33: 
   34: Deadlines and directions for students' applications to the Google
   35: Summer-of-Code can be found
   36: [on the Google pages](http://code.google.com/soc/).
   37: 
   38: # Application process
   39: 
   40: To make the job of sorting out proposals and applications for
   41: NetBSD-related projects, e.g. in the Google Summer-of-Code, easier for us,
   42: there are a few questions that we would like to see answered.
   43: 
   44: If you are interested in working on any of the projects below, please
   45: contact the mailing list referenced on each item, and possibly answer as
   46: many questions from our [[project application guidelines|application]] as
   47: possible.  The interested developers will be glad to respond to you there.
   48: 
   49: **Please note that Google Summer-of-Code projects are a full (day-) time job.**
   50: 
   51: A positive mid-term evaluation is only possible if usable code has been
   52: committed by that time.  Make sure your schedule allows for this.
   53: 
   54: # Kernel-level projects
   55: 
   56: ## Easy
   57: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:kernel) and tagged(difficulty:easy)"]]
   58: 
   59: ## Medium
   60: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:kernel) and tagged(difficulty:medium)"]]
   61: 
   62: ## Hard
   63: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:kernel) and tagged(difficulty:hard)"]]
   64: 
   65: # Userland projects
   66: 
   67: ## Easy
   68: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:userland) and tagged(difficulty:easy)"]]
   69: 
   70: ## Medium
   71: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:userland) and tagged(difficulty:medium)"]]
   72: 
   73: ## Hard
   74: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:userland) and tagged(difficulty:hard)"]]
   75: 
   76: # pkgsrc projects
   77: 
   78: ## Easy
   79: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:pkgsrc) and tagged(difficulty:easy)"]]
   80: 
   81: ## Medium
   82: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:pkgsrc) and tagged(difficulty:medium)"]]
   83: 
   84: ## Hard
   85: [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:pkgsrc) and tagged(difficulty:hard)"]]
   86: 
   87: # Comments
   88: 
   89: We are trying to be fair; expect easy projects to require less knowledge and skill, but quite a bit of work.
   90: 
   91: 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.
   92: 
   93: 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.
   94: 
   95: 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.