Diff for /wikisrc/projects/code-in.mdwn between versions 1.33 and 1.34

version 1.33, 2012/10/20 12:27:09 version 1.34, 2012/10/21 10:15:41
Line 9  Even if you don't want to attend the Cod Line 9  Even if you don't want to attend the Cod
   
 Previous events by Google: [Code-In 2010](http://code.google.com/opensource/gci/2010-11/index.html), [Ghop 2007](http://code.google.com/opensource/ghop/2007-8/)  Previous events by Google: [Code-In 2010](http://code.google.com/opensource/gci/2010-11/index.html), [Ghop 2007](http://code.google.com/opensource/ghop/2007-8/)
   
   Previous organizations accepted for Code-In: [Code-In 2010](http://www.google-melange.com/gci/accepted_orgs/google/gci2010) [Code-In 2011](http://www.google-melange.com/gci/accepted_orgs/google/gci2011)
   
 ## Goals as stated by Google  ## Goals as stated by Google
 1. **Code**: Tasks related to writing or refactoring code  1. **Code**: Tasks related to writing or refactoring code
 1. **Documentation/Training**: Tasks related to creating/editing documents and helping others learn more  1. **Documentation/Training**: Tasks related to creating/editing documents and helping others learn more
Line 34  Used tags are (categories are not tagged Line 36  Used tags are (categories are not tagged
 ## Prerequisites  ## Prerequisites
 Altough there are several tasks involving prerequisites, you should read the text for the amount they are necessary in. Maybe there is a Latex prerequisite, but we could provide you with the Latex knowledge you need to fulfill the task.  Altough there are several tasks involving prerequisites, you should read the text for the amount they are necessary in. Maybe there is a Latex prerequisite, but we could provide you with the Latex knowledge you need to fulfill the task.
   
   For all the tasks involving prerequisites, you should bring in some experience in this field (like typesetting at all for Latex, and minor or very small coding work in the required languages for the coding tasks). We will answer you questions regarding the actual coding, so don't hesitate to ask for a task when you do not fully fulfill the prerequisites.
   
 ## Proposed tasks  ## Proposed tasks
 ### Documentation  ### Documentation
   
Line 114  Altough there are several tasks involvin Line 118  Altough there are several tasks involvin
   *Tag*: howto      *Tag*: howto  
   *Tag*: system    *Tag*: system
   
   * **Task: Howto: Protecting your system with veriexec**: There already is [a chapter in the Guide](http://netbsd.org/docs/guide/en/chap-veriexec.html) about veriexec, but there is no comprehensive guide how to activate it and how to check in all files in the distribution (there is [veriexecgen(8)](http://netbsd.gw.com/cgi-bin/man-cgi?veriexecgen++NetBSD-current) for this.  
     Your task is to write a howto describing evrything a user needs to know and needs to do to have a secure system with veriexec.  
     *Tag*: howto
     *Tag*: system
   
 * **Task: Intro: Disk and partition management with NetBSD**: Additionally to the gpt and mbr confusion, NetBSD has two other systems that add complexity to disk management: Disk wedges (dk(4)) and Unix disklabels (disklabel(5)).    * **Task: Intro: Disk and partition management with NetBSD**: Additionally to the gpt and mbr confusion, NetBSD has two other systems that add complexity to disk management: Disk wedges (dk(4)) and Unix disklabels (disklabel(5)).  
   You should write an article that introduces the reader to these systems, how they interact, and what their use cases are.      You should write an article that introduces the reader to these systems, how they interact, and what their use cases are.  
   *Tag*: howto      *Tag*: howto  
Line 158  Altough there are several tasks involvin Line 167  Altough there are several tasks involvin
   Possible appliances would be:    Possible appliances would be:
   * **router** - NetBSD is very well suited for router appliances and often used for that. There is a special task which is about creating a howto how to configure npf and comparing the different firewall solutions NetBSD offers. This task would rather be about everything around, like the routing part, securing the machine, network management (e.g. for wireless access points), and maybe only one example configuration for the firewall (especially NATting). A good example for an existing appliance is pfSense    * **router** - NetBSD is very well suited for router appliances and often used for that. There is a special task which is about creating a howto how to configure npf and comparing the different firewall solutions NetBSD offers. This task would rather be about everything around, like the routing part, securing the machine, network management (e.g. for wireless access points), and maybe only one example configuration for the firewall (especially NATting). A good example for an existing appliance is pfSense
   * **file server** - NetBSD is also excellent as a file server, may it be either with nfs, smb, http, ftp or ftp over ssh as the transfer protocol. Your task would be to describe the packages which exist in pkgsrc and in NetBSD's base, and choose one special scenario for each protocol and give example configurations of the services. You should also mention RAIDframe, lvm and cgd briefly and what their use cases are. A good example for an existing appliance is FreeNAS or Apple Time Capsule (already running NetBSD).    * **file server** - NetBSD is also excellent as a file server, may it be either with nfs, smb, http, ftp or ftp over ssh as the transfer protocol. Your task would be to describe the packages which exist in pkgsrc and in NetBSD's base, and choose one special scenario for each protocol and give example configurations of the services. You should also mention RAIDframe, lvm and cgd briefly and what their use cases are. A good example for an existing appliance is FreeNAS or Apple Time Capsule (already running NetBSD).
   Every howto for an appliance is considered a single task.    
   * **backup server** - though somewhat similar to a file server, a backup server has different requirements. On the one hand, you have to think about how to connect effectively for backups, e.g. with rsync or other special backup protocols. On the other hand, you have to take special care for data integrity and data security. You should also take file system snapshots into account.    * **backup server** - though somewhat similar to a file server, a backup server has different requirements. On the one hand, you have to think about how to connect effectively for backups, e.g. with rsync or other special backup protocols. On the other hand, you have to take special care for data integrity and data security. You should also take file system snapshots into account.
   
     Every howto for an appliance is considered a single task.  
   As a special task, you could also create a shell script that fulfills the steps you mentioned in your howto, such that the user only has to execute this script to get an appliance. The prerequisite is only for this task.      As a special task, you could also create a shell script that fulfills the steps you mentioned in your howto, such that the user only has to execute this script to get an appliance. The prerequisite is only for this task.  
   If you can think of more possible appliances, maybe you can also use this as a task. If you want to work on a larger project (i.e. providing a whole derivate with one of these tasks), just tell us.      If you can think of more possible appliances, maybe you can also use this as a task. If you want to work on a larger project (i.e. providing a whole derivate with one of these tasks), just tell us.  
   *Prerequisites*: sh      *Prerequisites*: sh  
Line 338  Altough there are several tasks involvin Line 347  Altough there are several tasks involvin
   *Tag*: man    *Tag*: man
   
 * **Task: Write a markdown browser**: Markdown is the most widespread cleartext markup language, also used in the NetBSD wiki. Though it is already very well readable, some markups used are not as good and it would be nice to have them applicable directly. Looking at Markdown-rendered HTML is also not an option as it has too much overhead.    * **Task: Write a markdown browser**: Markdown is the most widespread cleartext markup language, also used in the NetBSD wiki. Though it is already very well readable, some markups used are not as good and it would be nice to have them applicable directly. Looking at Markdown-rendered HTML is also not an option as it has too much overhead.  
   This project is about researching the possibility of writing a Markdown browser for the shell. This should not be much work and most probably work.      This project is about researching the possibility of writing a Markdown browser for the shell and if it is possible, provide a structure such that somebody else could pick up the work and start coding it. This should not be much work and most probably work.  
   Then, you have to think about a user interface. You want to view a text (scrollable), but also offer the possibility of having links and opening new files, including a small "browser history".      Then, you have to think about a user interface. You want to view a text (scrollable), but also offer the possibility of having links and opening new files, including a small "browser history".  
   Considered as a second task, you could write a reference implementation for this browser. For the finished browser, we would need either an sh implementation if this is not too difficult or error-prone, or a C implementation. But for this project, you can take any language you want, sh and C just would be the preferred way.      Considered as a second task, you could write a reference implementation for this browser. For the finished browser, we would need either an sh implementation if this is not too difficult or error-prone, or a C implementation. But for this project, you can take any language you want, sh and C just would be the preferred way.  
   This project is intended to be included in pkgsrc, in the long run maybe in src. Anyway, it would be a very nice project for the whole developer community in the long run.      This project is intended to be included in pkgsrc, in the long run maybe in src. Anyway, it would be a very nice project for the whole developer community in the long run.  
Line 358  Altough there are several tasks involvin Line 367  Altough there are several tasks involvin
   *Tag*: wiki    *Tag*: wiki
   *Tag*: ui    *Tag*: ui
   
   
 ### User Interface  ### User Interface
   
 * **Task: Create NetBSD wallpapers**: Currently, there are nearly no NetBSD wallpapers. The combination of beastie, the flag and the old logo (daemons on old computers), plus the very smooth NetBSD colours (orange, grey, white) should be a resource for nice wallpapers.    * **Task: Create NetBSD wallpapers**: Currently, there are nearly no NetBSD wallpapers. The combination of beastie, the flag and the old logo (daemons on old computers), plus the very smooth NetBSD colours (orange, grey, white) should be a resource for nice wallpapers.  
Line 393  Altough there are several tasks involvin Line 403  Altough there are several tasks involvin
   *Tag*: graphics      *Tag*: graphics  
   *Tag*: ui    *Tag*: ui
   
   * **Task: Create a NetBSD poster**: NetBSD advocacy material is used on fairies where NetBSD usually has its own booth. To make the presentation more attractive, a nice poster (in format A0) would be nice.  
     This task can be fulfilled multiple times. You can either create different posters advocating different aspects of NetBSD, or just create graphical posters.  
     *Tag*: graphics
   

Removed from v.1.33  
changed lines
  Added in v.1.34


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