File:  [NetBSD Developer Wiki] / wikisrc / projects / gsoc.mdwn
Revision 1.25: download - view: text, annotated - select for diffs
Fri Jul 16 09:36:15 2021 UTC (4 months, 2 weeks ago) by wiki
Branches: MAIN
CVS tags: HEAD
auto

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