File:  [NetBSD Developer Wiki] / wikisrc / projects / code-in.mdwn
Revision 1.18: download - view: text, annotated - select for diffs
Fri Oct 22 10:38:40 2010 UTC (7 years, 1 month ago) by asau
Branches: MAIN
CVS tags: HEAD
Expand on thin client.

    1: # Google Code-In (GCI) project ideas
    2: 
    3: <http://code.google.com/opensource/gci/2010-11/index.html>
    4: 
    5: Google ran a similar event a couple of years ago, see <http://code.google.com/opensource/ghop/2007-8/> for details and perhaps snitch some ideas from there?
    6: 
    7: ## Goals as stated by Google
    8: 1. Code: Tasks related to writing or refactoring code
    9: 1. Documentation: Tasks related to creating/editing documents
   10: 1. Outreach: Tasks related to community management and outreach/marketing
   11: 1. Quality Assurance: Tasks related to testing and ensuring code is of high quality
   12: 1. Research: Tasks related to studying a problem and recommending solutions
   13: 1. Training: Tasks related to helping others learn more
   14: 1. Translation: Tasks related to localization
   15: 1. User Interface: Tasks related to user experience research or user interface design and interaction
   16: 
   17: ## Proposed areas
   18: ### Desktop project (QA, UI, Doc)
   19: 
   20: Try out various desktop scenarios: KDE, GNOME, XFCE.
   21: 
   22: Install software, configure, document, tune.
   23: 
   24: Make it good-looking, I mean _really_ good-looking.
   25: 
   26: Describe problems you meet, sort them out (file problem reports as necessary).
   27: 
   28: ### Document time and calendar formats and functions and their relations (Doc, QA)
   29: 
   30: We have "time_t", "struct timespec", "struct timeval", "struct tm", and so on.
   31: 
   32: Document all of them as time(5) so that one could have overview of those.
   33: 
   34: We have time zone sensitive and time zone independent representations too,
   35: figuring out conversions between local time and UTC from manual pages is hard.
   36: This is to be addressed too.
   37: 
   38: This requires some programming skills, some knowledge of C in particular.
   39: 
   40: ### Embedded project (Doc, Research)
   41: 
   42: Describe and document some embedded usage,
   43: e.g. making NetBSD run on machine without:
   44: 
   45: * keyboard and video ports
   46: * above and serial port
   47: 
   48: #### Possible embedded usage
   49: 
   50: * Thin client: rdesktop or vnc to hardcoded server
   51: * Home or SOHO router (wireless access point)
   52: * Home or SOHO file storage
   53: * Home or SOHO print server
   54: 
   55: It is preferred if NetBSD installation uses the least possible resources.
   56: (E.g. try making it boot over network, or consider that it is to be made so in future.)
   57: 
   58: #### More notes on embedded systems
   59: 
   60: ##### Router
   61: 
   62: Take any SOHO router as example.
   63: 
   64: Adapt pfSense? Similar software?
   65: 
   66: ### Thin client / Kiosk
   67: 
   68: Build thin client.
   69: 
   70: * install and configure graphical system (X server)
   71: * make your NetBSD autologin and launch some application (imagine a kind of kiosk or game console)
   72: * make your NetBSD ask login in graphical mode
   73: * make your NetBSD autologin and launch graphical application
   74: * configure and install VNC server
   75: * make your NetBSD connect to VNC server
   76: * configure and install RDP server
   77: * make your NetBSD connect to RDP server
   78: * boot your client over network
   79: 
   80: It is preferred if NetBSD installation uses the least possible resources.
   81: 
   82: ### File server
   83: Build personal file server.
   84: 
   85: Ideally, it should present HTTP(S), FTP(S), and SMB access to data.
   86: Consider other access methods (SFTP, NFS, AFS/CODA, AppleTalk).
   87: 
   88: Ideally, it should implement web interface.
   89: 
   90: Bonus points if you make it work like Apple Time Capsule (already running NetBSD) or better,
   91: e.g. implement periodic file system snapshots, 
   92: 
   93: Separate tasks:
   94: 
   95: * provide access to your files via HTTP
   96: * provide access to your files via FTP
   97: * provide access to your files via SMB
   98: * provide access to your files via NFS
   99: * provide access to your files via SFTP
  100: * create periodic file system snapshots on your NetBSD
  101: * learn how to perform automatic periodic tasks
  102: * make your NetBSD perform periodic file system snapshots
  103: * try doing anything/everything above on headless system
  104: * try automatising anything/everything above
  105: 
  106: ### Backup and Recovery (Research, Doc, QA, Code)
  107: 
  108: #### Incremental backup scenario
  109: 
  110: Document it. Try different plans.
  111: 
  112: #### Recovery from bare iron (QA, Doc, Code)
  113: 
  114: Consider installation recovery scenario from bare system to configured server.
  115: 
  116: Try automatizing it.
  117: 
  118: #### Unattended installation (Research, Code)
  119: 
  120: Like above only using installation tools.
  121: 
  122: 
  123: ### Live USB Flash image (Doc, Outreach, Code)
  124: 
  125: Perform and document how one does it.
  126: 
  127: Script it if possible.
  128: 
  129: Script cross-buildin if possible.
  130: 
  131: Consider thin client.
  132: 
  133: ### Installation tools (QA, Research, Doc, Code)
  134: 
  135: Try creating bootable media using fdisk, disklabel, installboot.
  136: Decribe experience, propose improvements, implement them.
  137: 
  138: Build NetBSD on any other OS at your choice: FreeBSD, Linux, NT, or OSX.
  139: 
  140: Try creating bootable media using tools built on another OS.
  141: Decribe experience, propose improvements, implement them.
  142: 
  143: Tools affected
  144:  
  145: * fdisk
  146: * disklabel
  147: * installboot
  148: * perhaps others
  149: 
  150: For hardcore hackers (those wishing to learn how the stuff works).
  151: 
  152: ### System Library project (Code, Doc, QA, Research)
  153: 
  154: Add a function call to a system library.
  155: The function call does not need to be immediately useful (ideally we should provide several
  156: suggestions) and in fact should not be very complex as the project contains the following
  157: tasks with varying skills
  158: 
  159: * produce C code of function
  160: * bump library minor version
  161: * write nroff manpage
  162: * handle Makefile changes
  163: * handle set list changes
  164: * write ATF testcase
  165: 
  166: ### Tests projects (Code, QA)
  167: 
  168: Create ATF tests for a section of library routines, such as (please add.. )
  169: 
  170: * string(3)
  171: * bluetooth(3)
  172: * sdp_data(3)
  173: 
  174: ### PR projects (Code, Research)
  175: 
  176: Create a fix for PR#...
  177: 
  178: (please list any PRs that you think are easily fixable but just require a bit
  179: of time that you don't have)
  180: 

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