File:  [NetBSD Developer Wiki] / wikisrc / projects / code-in_2012.mdwn
Revision 1.1: download - view: text, annotated - select for diffs
Wed Jan 16 12:04:01 2013 UTC (10 years, 10 months ago) by jdf
Branches: MAIN
CVS tags: HEAD
Add a page for GCi 2012 to integrate the work which has been done and sum up
our experiences.

    1: # Google Code-In 2012 (GCI)
    3: **Contents**
    4: [[!toc levels=4]]
    6: ## Introduction
    7: Code-In was running till January 14th. This page now contains the list of tasks which were actually done.
    8: You can see the results (open tasks as well as closed ones) [on the Google Melange]( page. There were 88 tasks done and 23 were left open.
   10: We provided a [Virtualbox]( image for testing, such students didn't have to spend time on installing the system when they just wanted to complete a task where they needed NetBSD running.
   12: Previous events by Google: [Code-In 2010](, [Ghop 2007](
   14: Previous organizations accepted for Code-In: [Code-In 2010]( [Code-In 2011](
   16: There is [information from Google]( about what is suitable as a task for Code-In.
   18: ## Goals as stated by Google
   19: 1. **Code**: Tasks related to writing or refactoring code
   20: 1. **Documentation/Training**: Tasks related to creating/editing documents and helping others learn more
   21: 1. **Outreach/Research**: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
   22: 1. **Quality Assurance**: Tasks related to testing and ensuring code is of high quality
   23: 1. **User Interface**: Tasks related to user experience research or user interface design and interaction
   25: ## Lessons learned
   26: The effort needed for Code-In struck us unexpected. There were several things to be learned about Code-In and about the kind of work that can be done in the scope of Code-In.
   28: ### Coding tasks are interesting
   29: The students are mostly interested in coding tasks. They do *not* want to write documentation, and they don't want to research things.
   30: With coding tasks, students would even spend more time on a task than they would do with something else, and maybe even stick to that task when GCi has finished.
   32: ### Add maintenance tasks
   33: Another kind of task which was often claimed were the ones about maintenance jobs, in this case conversion of articles from XML to Markdown. They're easy to do, but require a lot of effort - suitable for GCi.
   35: ### Have a clear outline of the task
   36: Tasks with an unclear description often led to results which were not as expected. Students of this age are more used to have a task which has a clear result, and not something open.
   37: Though there were some good results, it's still difficult to understand the tasks and sometimes the tasks were only solved with the second or third approach.
   39: ### No creative tasks, but design tasks
   40: Don't do creative tasks, i.e. creating images. On the other side, the design or layout tasks went very well - so if you want to know how a student would imagine the interface for a program or website or book format you need, then make that a task - but be clear about the results and *what* you expect.
   41: You should have thought yourself about how you would do this in advance, such that you can explicitly state what requirements the task has. You'll get nice results with new ideas.
   43: ### Watch out for plagiarism
   44: Especially in the research or documentation tasks, you have to be careful about plagiarism. Several students just copied texts from other sources and tried to submit them.
   46: ### Don't add extra requirements
   47: When the student has to download or configure extra requirements first, the task gets much harder. You should not add tasks which rely on src, pkgsrc or pkgsrc-wip or whatever large or difficult extra things to do before being able to work on the task.
   49: ### Make tasks small projects
   50: The coding parts are more appealing when they are small autonomous projects. The tasks involving creating your own binary had a larger acceptance than the once which were about fixing bugs of existing programs.
   51: You can and should tasks for small programs even if you only want them for *research*, i.e. you want to look at the possibility of a larger project involving this. Even if the task is about another project, but which would or could add benefits for NetBSD, it is possible.
   53: ### Make stand-alone projects
   54: This is not the same as *making small projects*. The described small projects should be in such a way that you can run them on any operating system and they don't require a speical setup to be written, i.e. many preinstalled packages.
   55: The students are most likely not running NetBSD, and forcing them to install NetBSD, install some pkgsrc packages and spend time configuring the system discourages doing a task.
   56: Even the Virtualbox images were no great help for some of these tasks.
   58: ### Combine tasks to a larger project
   59: Maybe contrary to *making small projects*, tasks should have a connection. Students are more engaged if they did something, and when approving the work you already point them to other tasks which are similar to the one they just did, or work together with this one.
   61: ### Be clear about your expected formats
   62: You should be very clear about the formats you expect for input! If there is an image, tell t hem to upload the "sources" (gimp xcf file or so); if there is a text, it should be plain-text; if it is a program, the final submission should be an archive with the code and not a link to github.
   64: ### Stay in touch with the students
   65: The best way of communication with the students is via IRC. Everything else is too slow, and when a task is meant to be 48 hours, but half of the time is spent waiting for communication, the task is likely to fail or waste student's time.
   67: ### Look into the tasks yourself before submitting them
   68: Though it might be charming - when you want students to fix a PR, you should look at the bug yourself and have a slight idea how to fix it before submitting it. There was a task which was not possible to fix (for the student) and was duplicate. And the students might have questions and then having to research things yourself before you can help is not good.
   70: Even with all the other tasks, you should have an idea what you want, and what effort it requires. There were some tasks which resulted in much work though they seemed easy in the beginning, while other tasks stated as difficult could be performed within a few minutes.
   72: ### Don't underestimate the required effort!
   73: You should *not* underestimate the effort needed by Code-In.
   74: On the one hand, when you're young, you're not as patient as later. Waiting several hours to get a task confirmed is a lot of time in a student's mind.
   76: On the other hand, there was a great run in the first week of Code-In. You have to read several tens of mails every hour, especially in the beginning.
   78: When a student needs help, you have to care for him and help him with that, even with configuring the system.
   80: ### Be demanding
   81: If you have an engaged student, you can be demanding. Don\'t hesitate to send back his work and be explicit about what you don\'t like. But be careful you don\'t frighten him. There were also students which just unclaimed a task because they didn\'t understand the review.
   83: ## Fulfilled tasks
   85: The work done by GCi has not yet been integrated to NetBSD. Especially the documentation tasks have to be put into the wiki, but also need modifications in the NetBSD website infrastructure.
   87: These are the tasks which were completed:
   89:  * [Howto: Running a webserver with Apache](
   90:  * [Intro: Disk and partition management with NetBSD](
   91:  * [Convert articles from the website to wiki articles](
   92:  * [Using the framebuffer in NetBSD](
   93:  * [Convert the encrypted iscsi article to markdown](
   94:  * [Research POSIX compliance](
   95:  * [Create NetBSD slide templates (OpenOffice)](
   96:  * [Try out RFB/VNC software on NetBSD](
   97:  * [Fix bug bin/41049: usermod -g =uid testuser does not create group as indicated by man page](
   98:  * [Survey documentation structure of other projects](
   99:  * [Create NetBSD slide templates (Latex)](
  100:  * [Describe the format of usermgmt.conf](
  101:  * [Create a small markdown wiki CGI](
  102:  * [Try out VoIP software](
  103:  * [Rewrite system configuration in the guide](
  104:  * [Create smaller NetBSD artworks](
  105:  * [Howto: Using LVM to manage your disks](
  106:  * [Create NetBSD wallpapers](
  107:  * [Create a NetBSD poster](
  108:  * [Convert the security processes to markdown](
  109:  * [Write apropos branch to search through Markdown documentation](
  110:  * [Convert the tracking current guide to markdown](
  111:  * [Describe what a NetBSD installation does](
  112:  * [Create lists of software needed for a desktop system](
  113:  * [Create an icon set for NetBSD - research](
  114:  * [Create a NetBSD poster](
  115:  * [Describe how to run NetBSD headless](
  116:  * [Create ATF tests](
  117:  * [Research and write a Markdown style guide](
  118:  * [Compare NetBSD with other operating systems of its kind](
  119:  * [Setup single sign-on (SSO) service using LDAP](
  120:  * [Create an overview of the NetBSD kernel source layout](
  121:  * [Convert the PUFFS guide to markdown](
  122:  * [Create an overview of the NetBSD src layout](
  123:  * [Try out XMPP software](
  124:  * [Write a Markdown - Latex converter](
  125:  * [Research terminfo(5) keycodes](
  126:  * [Create an overview of the NetBSD releases](
  127:  * [Fix bug install/17792: Install process order - network verses disk](
  128:  * [Investigate necessary documentation markup](
  129:  * [Convert the Xen Howto to markdown](
  130:  * [Write a mail wrapper](
  131:  * [Version the documentation](
  132:  * [Create an overview of NetBSD documentation](
  133:  * [Research POSIX compliance](
  134:  * [Howto: Getting in touch with NetBSD](
  135:  * [Make OpenDJ run on NetBSD](
  136:  * [Describe how to create a NetBSD live flash drive](
  137:  * [Convert the NetBSD Guide from DocBook to Markdown](
  138:  * [Survey documentation structure of other projects](
  139:  * [Howto: How to get a graphical environment on NetBSD](
  140:  * [Howto: Update the system from binaries](
  141:  * [Try out VoIP software](
  142:  * [Create NetBSD wallpapers](
  143:  * [Create an overview of the NetBSD server layout](
  144:  * ["Convert the CD-ROM creation guide to markdown](
  145:  * [Howto: Dual-boot NetBSD](
  146:  * [Create smaller NetBSD artworks](
  147:  * [Create NetBSD wallpapers](
  148:  * [Document different time structures](
  149:  * [Describe how to backup NetBSD](
  150:  * [Convert installation notes to markdown](
  151:  * [Create a concept for a documentation browser](
  152:  * [Create a NetBSD book layout](
  153:  * [Fix bug bin/47065: /bin/sh returns success for Bad file descriptor](
  154:  * [Create list of available VoIP client software](
  155:  * [Repair vnconfig(8)'s return codes](
  156:  * [Measure startup time](
  157:  * [Fix bug bin/46579: ifconfig prints unnecessary message when deleting interface](
  158:  * [Add an web interface to apropos](
  159:  * [Make NetBSD a music or video player](
  160:  * [Create ATF tests](
  161:  * [Convert the Networking FAQ to markdown](
  162:  * [Multi-user graphical terminal server accessible by RFB/VNC](
  163:  * [Compare init systems with each other](
  164:  * [Write a markdown - curses converter](
  165:  * [Create NetBSD wallpapers](
  166:  * [Convert internals guide to markdown](
  167:  * [Convert the NetBSD X documentation to markdown](
  168:  * [Create security/pam-pgsql package](
  169:  * [Create ATF tests](
  170:  * [Create databases/nss-pgsql package](
  171:  * [Create and implement an ikiwiki design template](
  172:  * [Create and implement a design and templates for a small wiki](
  173:  * [Create and implement a design for a web application](
  174:  * [Write a markdown - Docbook converter](
  175:  * [Fix bug bin/47367: patch(1) mishandles Oops.rej](
  176:  * [Survey documentation structure of other projects](

CVSweb for NetBSD wikisrc <> software: FreeBSD-CVSweb