File:  [NetBSD Developer Wiki] / wikisrc / projects / code-in.mdwn
Revision 1.25: download - view: text, annotated - select for diffs
Sat Nov 6 09:47:38 2010 UTC (10 years, 10 months ago) by mbalmer
Branches: MAIN
CVS tags: HEAD
Put this into perspective.

    1: # Google Code-In (GCI) project ideas
    2: 
    3: Please note:  In late 2010, Google ran a program somewhat similar to
    4: Google Summer of Code, Google Code-In, for which we applied, but were
    5: not selected.
    6: 
    7: We keep our proposed ideas on this page for further reference, or as a starting
    8: point if you want to start working on NetBSD.
    9: 
   10: 
   11: <http://code.google.com/opensource/gci/2010-11/index.html>
   12: 
   13: 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?
   14: 
   15: ## Goals as stated by Google
   16: 1. Code: Tasks related to writing or refactoring code
   17: 1. Documentation: Tasks related to creating/editing documents
   18: 1. Outreach: Tasks related to community management and outreach/marketing
   19: 1. Quality Assurance: Tasks related to testing and ensuring code is of high quality
   20: 1. Research: Tasks related to studying a problem and recommending solutions
   21: 1. Training: Tasks related to helping others learn more
   22: 1. Translation: Tasks related to localization
   23: 1. User Interface: Tasks related to user experience research or user interface design and interaction
   24: 
   25: ## Proposed areas
   26: ### Desktop project (QA, UI, Doc)
   27: 
   28: #### Generic desktop
   29: 
   30: Try out various desktop scenarios: KDE, GNOME, XFCE.
   31: 
   32: Install software, configure, document, tune.
   33: 
   34: Make it good-looking, I mean _really_ good-looking.
   35: 
   36: Describe problems you meet, sort them out (file problem reports as necessary).
   37: 
   38: #### Home theater (QA, Doc)
   39: 
   40: Try simulating music player and/or video player.
   41: 
   42: See also in embedded projects.
   43: 
   44: ### Document time and calendar formats and functions and their relations (Doc, QA)
   45: 
   46: We have "time_t", "struct timespec", "struct timeval", "struct tm", and so on.
   47: 
   48: Document all of them as time(5) so that one could have overview of those.
   49: 
   50: We have time zone sensitive and time zone independent representations too,
   51: figuring out conversions between local time and UTC from manual pages is hard.
   52: This is to be addressed too.
   53: 
   54: This requires some programming skills, some knowledge of C in particular.
   55: 
   56: ### Embedded project (Doc, Research)
   57: 
   58: Describe and document some embedded usage,
   59: e.g. making NetBSD run on machine without:
   60: 
   61: * keyboard and video ports
   62: * above and serial port
   63: 
   64: #### Possible embedded usage
   65: 
   66: * Thin client: rdesktop or vnc to hardcoded server
   67: * Home or SOHO router (wireless access point)
   68: * Home or SOHO file storage
   69: * Home or SOHO print server
   70: 
   71: It is preferred if NetBSD installation uses the least possible resources.
   72: (E.g. try making it boot over network, or consider that it is to be made so in future.)
   73: 
   74: #### More notes on embedded systems
   75: 
   76: ##### Router
   77: 
   78: Take any SOHO router as example.
   79: 
   80: Adapt pfSense? Similar software?
   81: 
   82: ##### Home theater
   83: 
   84: Create music and/or video player. Perhaps desktop.
   85: 
   86: ### Thin client / Kiosk
   87: 
   88: Build thin client.
   89: 
   90: * install and configure graphical system (X server)
   91: * make your NetBSD autologin and launch some application (imagine a kind of kiosk or game console)
   92: * make your NetBSD ask login in graphical mode
   93: * make your NetBSD autologin and launch graphical application
   94: * configure and install VNC server
   95: * make your NetBSD connect to VNC server
   96: * configure and install RDP server
   97: * make your NetBSD connect to RDP server
   98: * boot your client over network
   99: * make your client boot from CD or USB Flash, or CF card
  100: 
  101: It is preferred if NetBSD installation uses the least possible resources.
  102: 
  103: ### File server
  104: Build personal file server.
  105: 
  106: Ideally, it should present HTTP(S), FTP(S), and SMB access to data.
  107: Consider other access methods (SFTP, NFS, AFS/CODA, AppleTalk).
  108: 
  109: Ideally, it should implement web interface.
  110: 
  111: Bonus points if you make it work like Apple Time Capsule (already running NetBSD) or better,
  112: e.g. implement periodic file system snapshots, 
  113: 
  114: Separate tasks:
  115: 
  116: * provide access to your files via HTTP
  117: * provide access to your files via FTP
  118: * provide access to your files via SMB
  119: * provide access to your files via NFS
  120: * provide access to your files via SFTP
  121: * create periodic file system snapshots on your NetBSD
  122: * learn how to perform automatic periodic tasks
  123: * make your NetBSD perform periodic file system snapshots
  124: * try doing anything/everything above on headless system
  125: * try automatising anything/everything above
  126: 
  127: ### Bluetooth access point (Doc, QA, Code)
  128: 
  129: * connect NetBSD to your phone (dial out)
  130: * connect your phone or other computer to NetBSD via bluetooth
  131: * provide different services via bluetooth connection ("push", network)
  132: 
  133: ### Backup and Recovery (Research, Doc, QA, Code)
  134: 
  135: #### Incremental backup scenario
  136: 
  137: Document it. Try different plans.
  138: 
  139: #### Recovery from bare iron (QA, Doc, Code)
  140: 
  141: Consider installation recovery scenario from bare system to configured server.
  142: 
  143: Try automatizing it.
  144: 
  145: #### Unattended installation (Research, Code)
  146: 
  147: Like above only using installation tools.
  148: 
  149: 
  150: ### Live USB Flash image (Doc, Outreach, Code)
  151: 
  152: Perform and document how one does it.
  153: 
  154: Script it if possible.
  155: 
  156: Script cross-buildin if possible.
  157: 
  158: Consider thin client.
  159: 
  160: ### Installation tools (QA, Research, Doc, Code)
  161: 
  162: Try creating bootable media using fdisk, disklabel, installboot.
  163: Decribe experience, propose improvements, implement them.
  164: 
  165: Build NetBSD on any other OS at your choice: FreeBSD, Linux, NT, or OSX.
  166: 
  167: Try creating bootable media using tools built on another OS.
  168: Decribe experience, propose improvements, implement them.
  169: 
  170: Tools affected
  171:  
  172: * fdisk
  173: * disklabel
  174: * installboot
  175: * perhaps others
  176: 
  177: For hardcore hackers (those wishing to learn how the stuff works).
  178: 
  179: ### Audio/Video broadcasting (network radio/TV broadcasting)
  180: 
  181: Build audio and/or video broadcasting server.
  182: 
  183: ### Telephony
  184: 
  185: Become VoIP provider!
  186: 
  187: ### Build system QA (QA, Code, Research)
  188: 
  189: Check all MK* variables, check how they affect builds,
  190: suggest improvements or removal.
  191: 
  192: ### System Library project (Code, Doc, QA, Research)
  193: 
  194: Add a function call to a system library.
  195: The function call does not need to be immediately useful (ideally we should provide several
  196: suggestions) and in fact should not be very complex as the project contains the following
  197: tasks with varying skills
  198: 
  199: * produce C code of function
  200: * bump library minor version
  201: * write nroff manpage
  202: * handle Makefile changes
  203: * handle set list changes
  204: * write ATF testcase
  205: 
  206: ### Tests projects (Code, QA)
  207: 
  208: Create ATF tests for a section of library routines, such as:
  209: 
  210: * [[!template id=man name="atomic_ops" section="3"]]
  211: * [[!template id=man name="bitstring" section="3"]]
  212: * [[!template id=man name="bluetooth" section="3"]]
  213: * [[!template id=man name="cdbr" section="3"]] and [[!template id=man name="cdbw" section="3"]]
  214: * [[!template id=man name="inet" section="3"]] and [[!template id=man name="inet_net" section="3"]]
  215: * [[!template id=man name="ethers" section="3"]], [[!template id=man name="iso_addr" section="3"]] and [[!template id=man name="link_addr" section="3"]]
  216: * [[!template id=man name="regex" section="3"]]
  217: * [[!template id=man name="sdp_data" section="3"]]
  218: * [[!template id=man name="ssp" section="3"]]
  219: * [[!template id=man name="string" section="3"]]
  220: * [[!template id=man name="strings" section="3"]]
  221: * [[!template id=man name="strtod" section="3"]], [[!template id=man name="strtol" section="3"]], [[!template id=man name="strtoul" section="3"]] and [[!template id=man name="strtoull" section="3"]]
  222: * [[!template id=man name="uuid" section="3"]]
  223: * (please add..)
  224: 
  225: ### PR projects (Code, Research)
  226: 
  227: Create a fix for PR#...
  228: 
  229: (please list any PRs that you think are easily fixable but just require a bit
  230: of time that you don't have)
  231: 
  232: ### Documentation projects (Doc, Outreach)
  233: 
  234: #### Save all useful information from closed wiki.NetBSD.SE
  235: 
  236: Go over NetBSD.SE snapshot, check pages for valid and useful information,
  237: move all relevant bits to to-be-official NetBSD wiki.

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