File:  [NetBSD Developer Wiki] / wikisrc / projects / code-in.mdwn
Revision 1.2: download - view: text, annotated - select for diffs
Thu Oct 21 11:00:38 2010 UTC (10 years, 11 months ago) by asau
Branches: MAIN
CVS tags: HEAD
Add markup.

    1: # Google Code-In (GCI) project ideas
    2: 
    3: <http://code.google.com/opensource/gci/2010-11/index.html>
    4: 
    5: ## Goals as stated by Google
    6: 1. Code: Tasks related to writing or refactoring code
    7: 1. Documentation: Tasks related to creating/editing documents
    8: 1. Outreach: Tasks related to community management and outreach/marketing
    9: 1. Quality Assurance: Tasks related to testing and ensuring code is of high quality
   10: 1. Research: Tasks related to studying a problem and recommending solutions
   11: 1. Training: Tasks related to helping others learn more
   12: 1. Translation: Tasks related to localization
   13: 1. User Interface: Tasks related to user experience research or user interface design and interaction
   14: 
   15: ## Proposed areas
   16: ### Desktop project (QA, UI, Doc)
   17: 
   18: Try out various desktop scenarios: KDE, GNOME, XFCE.
   19: 
   20: Install software, configure, document, tune.
   21: 
   22: Make it good-looking, I mean _really_ good-looking.
   23: 
   24: Describe problems you meet, sort them out (file problem reports as necessary).
   25: 
   26: ### Document time and calendar formats and functions and their relations (Doc, QA)
   27: 
   28: We have "time_t", "struct timespec", "struct timeval", "struct tm", and so on.
   29: Document all of them as time(5) so that one could have overview of those.
   30: 
   31: This requires some programming skills, some knowledge of C in particular.
   32: 
   33: ### Embedded project (Doc, Research)
   34: 
   35: Describe and document some embedded usage,
   36: e.g. making NetBSD run on machine without:
   37: 
   38: * keyboard and video ports
   39: * above and serial port
   40: 
   41: Consider unattended installation as subproject or similar project.
   42: 
   43: Consider thin client as subproject or similar project.
   44: 
   45: ### Live USB Flash image (Doc, Outreach, Code)
   46: 
   47: Perform and document how one does it.
   48: 
   49: Script it if possible.
   50: 
   51: Script cross-buildin if possible.
   52: 
   53: Fix fdisk, installboot and other tools as needed (for hardcore hackers).
   54: 
   55: Consider thin client.

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