Diff for /wikisrc/projects/code-in.mdwn between versions 1.45 and 1.46

version 1.45, 2013/01/18 20:14:26 version 1.46, 2013/10/16 18:43:02
Line 100  Used tags are (categories are not tagged Line 100  Used tags are (categories are not tagged
   *Tag*: network      *Tag*: network  
   *Tag*: research    *Tag*: research
   
 * **Task: Survey documentation structure of other projects**: There are many open source projects which exist not only for years, but also for decades (which e.g. NetBSD also nearly does with 19 years). For all of them, documentation is an important issue, and most, if not all projects have not mastered writing documentation.    * **Task: Survey documentation structure of other projects**: There are many open source projects which exist not only for years, but also for decades (which e.g. NetBSD also has with 20 years). For all of them, documentation is an important issue, and most, if not all projects have not mastered writing documentation.  
   In this task, you have to choose on of the projects listed below. If you want to research another project not listed, please ask a judge about it.      In this task, you have to choose one of the projects listed below. If you want to research another project not listed, please ask a judge about it.  
   Then, you have to research the documentation of these projects (what sources are there, how are they used, which software do they use, which formatting language, etc. (what sources are there, how are they used, which software do they use, which formatting language, etc.), plus finding a way of determining the project's opinion of their documentation (a docs@ mailinglist might be a good start, like e.g. NetBSD-docs@NetBSD.org is). All in all, you should do nearly the same as the task "Create an overview of NetBSD documentation", except that you don't have to be that much in depth, but you should also research the technical and administrational background.      Then, you have to research the documentation of these projects (what sources are there, how are they used, which software do they use, which formatting language, etc. (what sources are there, how are they used, which software do they use, which formatting language, etc.), plus finding a way of determining the project's opinion of their documentation (a docs@ mailing list might be a good start, like e.g. NetBSD-docs@NetBSD.org is). All in all, you should do nearly the same as the task "Create an overview of NetBSD documentation", except that you don't have to be that much in depth, but you should also research the technical and administrative background.  
   In the end, you should write a paper with the results of the survey and a small text, at least one page at all.      In the end, you should write a paper with the results of the survey and a small text, at least one page at all.  
   This task can be fulfilled multiple times, once for each project.      This task can be fulfilled multiple times, once for each project.  
   *Projects*: FreeBSD, OpenBSD, DragonFly, Gentoo, Slackware, PostgreSQL      *Projects*: FreeBSD, OpenBSD, DragonFly, Gentoo, Slackware, PostgreSQL  
Line 122  Used tags are (categories are not tagged Line 122  Used tags are (categories are not tagged
   
 ### Quality Assurance  ### Quality Assurance
   
 * **Task: Research POSIX compliance**: POSIX is the (more or less) standard all Unixes orient on. It describes libraries to use as well as binaries every Unix should have (like cp, mv) and their behaviour.  * **Task: Research POSIX compliance**: POSIX is the (more or less) standard all Unixes orient on. It describes libraries to use as well as binaries every Unix should have (like cp, mv) and their behavior.
   You can find the standard on the Internet. Your task is to look for any non-trivial manpage (i.e., more than a few options) and research whether the NetBSD behaviour of this tool or library conforms to POSIX or not.      You can find the standard on the Internet. Your task is to look for any non-trivial man page (i.e., more than a few options) and research whether the NetBSD behavior of this tool or library conforms to POSIX or not.  
   You should then insert this part into a list and document whether it complies to POSIX and if not, which differences are there.      You should then insert this part into a list and document whether it complies to POSIX and if not, which differences are there.  
   As it is hard to determine the difficulty of a single part of the standard, this will be measured in lines. For every 1000 lines of the NetBSD versions of the manpages, this is one task.      As it is hard to determine the difficulty of a single part of the standard, this will be measured in lines. For every 1000 lines of the NetBSD versions of the man pages, this is one task.  
   The prerequisite is only for looking at libraries.      The prerequisite is only for looking at libraries.  
   *Prerequisite*: C (reading)      *Prerequisite*: C (reading)  
   *Tag*: research    *Tag*: research
   
 * **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). Also refer to the examples in /usr/share/examples/npf. 
   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 technical aspects of npf itself: What kind of rules and tables are there, how they are applied, etc.  
   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.      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 195  Used tags are (categories are not tagged Line 195  Used tags are (categories are not tagged
   *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.    * **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.      Your task is to write a howto describing everything a user needs to know and needs to do to have a secure system with veriexec.  
   *Tag*: howto      *Tag*: howto  
   *Tag*: system    *Tag*: system
   

Removed from v.1.45  
changed lines
  Added in v.1.46


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