File:  [NetBSD Developer Wiki] / wikisrc / projects / gsoc.mdwn
Revision 1.26: download - view: text, annotated - select for diffs
Wed Feb 16 19:57:45 2022 UTC (9 months, 3 weeks ago) by leot
Branches: MAIN
CVS tags: HEAD
Also mention 2021

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

CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb