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

version 1.32, 2012/10/20 10:29:06 version 1.33, 2012/10/20 12:27:09
Line 16  Previous events by Google: [Code-In 2010 Line 16  Previous events by Google: [Code-In 2010
 1. **Quality Assurance**: Tasks related to testing and ensuring code is of high quality  1. **Quality Assurance**: Tasks related to testing and ensuring code is of high quality
 1. **User Interface**: Tasks related to user experience research or user interface design and interaction  1. **User Interface**: Tasks related to user experience research or user interface design and interaction
   
   ## Used tags
 ## Proposed tasks  
   
 ### Used tags:  
 If you want to search for a tag, just search this site for "Tag: $TAGNAME".  If you want to search for a tag, just search this site for "Tag: $TAGNAME".
 Used tags are (categories are not tagged):  Used tags are (categories are not tagged):
   
Line 34  Used tags are (categories are not tagged Line 31  Used tags are (categories are not tagged
 * *ui* - tasks involving the user interface (mostly graphical)  * *ui* - tasks involving the user interface (mostly graphical)
 * *graphics* - tasks related to creating graphics  * *graphics* - tasks related to creating graphics
   
   ## 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.
   
   ## Proposed tasks
 ### Documentation  ### Documentation
   
 * **Task: Describe the format of usermgmt.conf**: The file usermgmt.conf contains default values used by user management tools (like useradd(8)). But currently, the manpage usermgmt.conf(5) contains only a description of the fields, but not the format of the file itself. So review code about what is possible (spaces, tabs, etc.) and create an EXAMPLE section.    * **Task: Describe the format of usermgmt.conf**: The file usermgmt.conf contains default values used by user management tools (like useradd(8)). But currently, the manpage usermgmt.conf(5) contains only a description of the fields, but not the format of the file itself. So review code about what is possible (spaces, tabs, etc.) and create an EXAMPLE section.  
Line 298  Used tags are (categories are not tagged Line 298  Used tags are (categories are not tagged
 * **Task: Howto: Configure npf**: The new NetBSD packet filter npf is a nice and well-scaling way to configure a firewall. Despite being there and functional, it does not have much documentation.    * **Task: Howto: Configure npf**: The new NetBSD packet filter npf is a nice and well-scaling way to configure a firewall. Despite being there and functional, it does not have much documentation.  
   The manpage of npf.conf(5) gives an introduction, but nothing that could be used as a howto: [npf.conf(5)](http://netbsd.gw.com/cgi-bin/man-cgi?npf.conf+5+NetBSD-current).      The manpage of npf.conf(5) gives an introduction, but nothing that could be used as a howto: [npf.conf(5)](http://netbsd.gw.com/cgi-bin/man-cgi?npf.conf+5+NetBSD-current).  
   The howto should contain a step-by-step introduction about how npf works, but also an introduction to the technics of npf itself: What kind of rules and tables are there, how they are applied, etc.      The howto should contain a step-by-step introduction about how npf works, but also an introduction to the technics of npf itself: What kind of rules and tables are there, how they are applied, etc.  
   There is already a [http://www.netbsd.org/~rmind/pub/npf_manual_netbsd_6.pdf](howto by rmind), this would have to be converted and checked against errors, and extended.      There is already a [howto by rmind](http://www.netbsd.org/~rmind/pub/npf_manual_netbsd_6.pdf), this would have to be converted and checked against errors, and extended.  
   *Tag*: howto      *Tag*: howto  
   *Tag*: network    *Tag*: network
   
Line 332  Used tags are (categories are not tagged Line 332  Used tags are (categories are not tagged
   As maybe Markdown is going to be in the source tree, we want to extend apropos to also be able to search through Markdown articles.      As maybe Markdown is going to be in the source tree, we want to extend apropos to also be able to search through Markdown articles.  
   Your task would be to research the possibility of creating another binary that is able to search through markdown pages, creating its own index file (mandb).      Your task would be to research the possibility of creating another binary that is able to search through markdown pages, creating its own index file (mandb).  
   If you are having fun with this, thinking about ways how to combine the two binaries into one single documentation search binary would be good.      If you are having fun with this, thinking about ways how to combine the two binaries into one single documentation search binary would be good.  
   [http://mail-index.netbsd.org/tech-userlevel/2012/02/01/msg006040.html](Mail announcing import of apropos)      [Mail announcint import of apropos](http://mail-index.netbsd.org/tech-userlevel/2012/02/01/msg006040.html)  
   *Prerequisites*: C      *Prerequisites*: C  
   *Tag*: research      *Tag*: research  
   *Tag*: man    *Tag*: man
Line 343  Used tags are (categories are not tagged Line 343  Used tags are (categories are not tagged
   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.  
   The prerequisites are only for the coding part.      The prerequisites are only for the coding part.  
   [http://fossil.instinctive.eu/libsoldout/index](libsoldout, a public-domain Markdown implementation in C)      [libsoldout, a public-domain Markdown implementation in C](http://fossil.instinctive.eu/libsoldout/index)  
   *Prerequisites*: C or sh      *Prerequisites*: C or sh  
   *Tag*: research      *Tag*: research  
   *Tag*: wiki      *Tag*: wiki  
   
   * **Task: Write a Markdown - PDF (or Latex) converter**: This task is not strictly for NetBSD, but another project named [libsoldout](http://fossil.instinctive.eu/libsoldout). libsoldout is a markdown converter written in C and published under public domain.
     Though there are already other tools which would do this task, they either have a licence that is not usable by NetBSD or have too many dependencies (like pandoc).  
     Your task is to write a converter from Markdown to Latex (or PDF, which might be a fairly large task), which is just specifying some tags you use for inserting and putting it in C code.  
     You can take the [html](http://fossil.instinctive.eu/libsoldout/artifact/fd100c723c722189d62fd9bf261d67db69240043) or the [mdoc](http://fossil.instinctive.eu/libsoldout/artifact/1e22b7962dfba92c28f4916609746045dbe29a90) converter as a template for this. Though this task seems large, the task itself is rather small. You have to analyze the converters for mdoc and html and replace their tags by the appropriate Latex ones.  
     If you're not as good with Latex, feel free to ask for the tags that are to replace.  
     *Prerequisites*: C Latex  
     *Tag*: research
     *Tag*: wiki
     *Tag*: ui
   
 ### User Interface  ### User Interface
   
Line 371  Used tags are (categories are not tagged Line 380  Used tags are (categories are not tagged
   *Tag*: graphics    *Tag*: graphics
   
 * **Task: Create NetBSD slide templates (Latex)**: NetBSD developers often hold presentations on conferences like the EuroBSDCon, BSDCan, etc.    * **Task: Create NetBSD slide templates (Latex)**: NetBSD developers often hold presentations on conferences like the EuroBSDCon, BSDCan, etc.  
   For all these occassions, people are using the [http://de.wikipedia.org/wiki/Latex](Latex typesetting system) beamer package, but using their own templates or the standard template.      For all these occassions, people are using the [Latex typesetting system](http://de.wikipedia.org/wiki/Latex) beamer package, but using their own templates or the standard template.  
   Your task would be to create a template that can be downloaded, included and then simply used such that NetBSD presentations have a NetBSD branding.    Your task would be to create a template that can be downloaded, included and then simply used such that NetBSD presentations have a NetBSD branding.
   This task is also a great chance to get used to the Latex package beamer or to Latex at all, it is usable for any presentations in school or university. So don't hesitate if you don't fulfill the prerequisite, if you want to learn, you can relatively fast do it and then complete this task.      This task is also a great chance to get used to the Latex package beamer or to Latex at all, it is usable for any presentations in school or university. So don't hesitate if you don't fulfill the prerequisite, if you want to learn, you can relatively fast do it and then complete this task.  
   *Prerequisite*: Latex      *Prerequisite*: Latex  
   *Tag*: graphics    *Tag*: graphics  
     *Tag*: ui
   
   * **Task: Create a NetBSD book layout**: NetBSD has several articles that could and are converted to PDF. While the final conversion and its methods is another task, having a nice book layout is necessary.  
     In this task, you have to research the different styles a NetBSD article would need (i.e., code blocks, other blockquotes, special quotes for commands, for manpages, etc.) and everything around like a front page, the font, etc.  
     You can deliver the specification either as a Latex style or exactly written with some example images.  
     *Tag*: graphics  
   *Tag*: ui    *Tag*: ui
   

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


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