Return to gsoc.mdwn CVS log

Up to [NetBSD Developer Wiki] / wikisrc / projects

web commit by spz

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