Annotation of wikisrc/projects/code-in.mdwn, revision 1.14

1.1       asau        1: # Google Code-In (GCI) project ideas
                      2: 
                      3: <http://code.google.com/opensource/gci/2010-11/index.html>
                      4: 
1.14    ! plunky      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: 
1.1       asau        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.
1.2       asau       21: 
1.1       asau       22: Install software, configure, document, tune.
1.2       asau       23: 
1.1       asau       24: Make it good-looking, I mean _really_ good-looking.
1.2       asau       25: 
1.1       asau       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.
1.5       asau       31: 
1.1       asau       32: Document all of them as time(5) so that one could have overview of those.
                     33: 
1.5       asau       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: 
1.1       asau       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:
1.2       asau       44: 
1.1       asau       45: * keyboard and video ports
                     46: * above and serial port
                     47: 
1.4       asau       48: #### Possible embedded usage
1.1       asau       49: 
1.4       asau       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: 
1.6       asau       58: #### More notes on embedded systems
                     59: ##### File server
                     60: It should present HTTP(S), FTP(S), and SMB access to data (must),
                     61: consider other access methods (SFTP, NFS, AFS/CODA, AppleTalk).
                     62: 
                     63: It should implement web interface.
                     64: 
                     65: Bonus points if you make it work like Apple Time Capsule (already running NetBSD) or better,
                     66: e.g. implement periodic file system snapshots, 
                     67: 
                     68: ##### Router
                     69: 
                     70: Take any SOHO router as example.
                     71: 
                     72: Adapt pfSense? Similar software?
                     73: 
1.4       asau       74: ### Unattended installation (Research, Doc, Code)
                     75: 
                     76: Consider installation recovery scenario from bare system to configured server.
1.1       asau       77: 
                     78: ### Live USB Flash image (Doc, Outreach, Code)
                     79: 
                     80: Perform and document how one does it.
                     81: 
                     82: Script it if possible.
                     83: 
                     84: Script cross-buildin if possible.
                     85: 
1.7       asau       86: Consider thin client.
                     87: 
1.11      asau       88: ### Installation tools (QA, Research, Doc, Code)
1.1       asau       89: 
1.11      asau       90: Try creating bootable media using fdisk, disklabel, installboot.
                     91: Decribe experience, propose improvements, implement them.
1.7       asau       92: 
1.11      asau       93: Build NetBSD on any other OS at your choice: FreeBSD, Linux, NT, or OSX.
1.12      asau       94: 
1.11      asau       95: Try creating bootable media using tools built on another OS.
                     96: Decribe experience, propose improvements, implement them.
                     97: 
                     98: Tools affected
                     99:  
                    100: * fdisk
                    101: * disklabel
                    102: * installboot
                    103: * perhaps others
                    104: 
                    105: For hardcore hackers (those wishing to learn how the stuff works).
1.8       plunky    106: 
                    107: ### System Library project (Code, Doc, QA, Research)
                    108: 
                    109: Add a function call to a system library.
                    110: The function call does not need to be immediately useful (ideally we should provide several
                    111: suggestions) and in fact should not be very complex as the project contains the following
                    112: tasks with varying skills
                    113: 
                    114: * produce C code of function
                    115: * bump library minor version
                    116: * write nroff manpage
                    117: * handle Makefile changes
                    118: * handle set list changes
                    119: * write ATF testcase
1.9       plunky    120: 
                    121: ### Tests projects (Code, QA)
                    122: 
                    123: Create ATF tests for a section of library routines, such as (please add.. )
                    124: 
                    125: * string(3)
                    126: * bluetooth(3)
                    127: * sdp_data(3)
1.10      plunky    128: 
                    129: ### PR projects (Code, Research)
                    130: 
                    131: Create a fix for PR#...
                    132: 
                    133: (please list any PRs that you think are easily fixable but just require a bit
                    134: of time that you don't have)
                    135: 

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