Diff for /wikisrc/projects/code-in.mdwn between versions 1.48 and 1.69

version 1.48, 2013/10/20 23:47:14 version 1.69, 2016/10/11 10:25:59
Line 41  also be read there. Line 41  also be read there.
 ## Tasks  ## Tasks
   
 There were some tasks left, and there might be more ideas over the following   There were some tasks left, and there might be more ideas over the following 
 year to participate in Code-In 2013 again.  year to participate in Code-In 2017 again.
   
 ## Used tags  ## 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".
Line 64  Used tags are (categories are not tagged Line 64  Used tags are (categories are not tagged
   
 ### Code  ### Code
   
   * **Task: Serve HTML man pages using NetBSD's "bozohttpd" server**
     NetBSD installs man pages in different formats, one of them being html pages.  The goal of this task is to write a Lua script for
     the [[!template id=man name="bozohttpd" section="8"]] web server, i.e. NetBSD's integrated webserver, that displays a webform where a man page section and the
     name of a man page can be entered (see [[!template id=man name="httpd" section="8"]]).
     When the form is submitted, the Lua script will do a lookup if there is a corresponding
     man page in html form and deliver to the web-browser.  Contact mbalmer@ if you have questions.
     *Prerequisites*: Lua, HTML.
     *Tag*: man
     *Tag*: service
     *Tag*: ui
   
 * **Task: Create ATF tests**: [[atf]] is the automatic test framework for NetBSD. We strive to have automatic tests for all the important parts of our system: libraries, syscalls, binaries, etc.    * **Task: Create ATF tests**: [[atf]] is the automatic test framework for NetBSD. We strive to have automatic tests for all the important parts of our system: libraries, syscalls, binaries, etc.  
   Your task is to write such tests. You should read the [[tutorial|atf]] about how to write an atf test, and then you can start testing things.      Your task is to write such tests. You should read the [[tutorial|atf]] about how to write an atf test, and then you can start testing things.  
   As testing is an endless task, here are just a few ideas about which items could be tested:    As testing is an endless task, here are just a few ideas about which items could be tested:
Line 81  Used tags are (categories are not tagged Line 92  Used tags are (categories are not tagged
   *Tag*: man      *Tag*: man  
   *Tag*: research    *Tag*: research
   
   * **Task: create a pkgsrc package**: choose one software package from the [categorized list](http://ftp.netbsd.org/pub/NetBSD/misc/asau/tasks), create pkgsrc package.
     Your task is to create a package, check that it runs, and describe how to do a [smoke test](http://en.wikipedia.org/wiki/Smoke_testing).
     For each software package there are three formal tasks of different complexity (unless noted):
     * make draft package that passes configure phase (medium complexity);
     * make draft package that passes build phase (medium complexity);
     * complete package that passes packaging checks and creates binary package (easy).
     *Tags*: code, pkgsrc
   
   * Avoiding TeX dependencies for [[!template id=pkg category="meta-pkgs" name="netbsd-www"]]
     It has been reported that one of obstacles when maintaining NetBSD documentation is the cost of update of tool packages.
     Surface analysis reveals that a lot of time may be spent on building TeX packages which are used to generate printable documentation in PostScript and PDF. The latter may be unneeded (e.g. when only HTML is of concern).
     The task is to drop dependency on TeX packages in the whole toolchain pulled by [[!template id=pkg category="meta-pkgs" name="netbsd-www"]] in order to make it optional, if it really matters.
     *Tags*: code, pkgsrc
   
   * Search engine (Lucene)
     Status: Reopened Time to complete: 96 hrs Mentors: Radoslaw Kujawa, Aleksej Saushev Tags: 
     These days we have to search for information not only on WWW but on our personal machines either. Your task is to research in setting up text search engine Lucene in any (or all, at your option) of use cases: just personal desktop, web site, mailing list archive.
     We have outdated work-in-progress package in pkgsrc-wip. Update it, make sure it works with OpenJDK7. Test it with all acceptable options. Preferrably, make it build from source as well.
     Provide instructions how to deploy Lucene itself and all needed components, if it isn't done automatically already.
     Provide instructions how to setup and test functionality.
     If possible, automate everything you can.
     It is possible, that you meet blocking problem. Good problem report (step-by-step instructions to reproduce, description of what expected and observed results are) and explanation why it constitutes blocking problem for this task are accepted as successful task completion.
     It is possible that some things are not essential to setup. Clear explanation why some requirement is not met is accepted.
     In case you have further questions when working on the task, don't hesitate to contact us on #netbsd-code.
     *Tags*: desktop, web, java, pkgsrc, code
   
   * Make ApacheDS run on NetBSD
     Traditionally directory services in open-source systems are built around OpenLDAP, which is tricky to setup. There exist alternative implementations of LDAP directory software. One of them is ApacheDS, but the software is written in Java, which brings different challenges.
     Provide instructions (step-by-step, where needed) how to make ApacheDS work on NetBSD, including instructions how to download ApacheDS itself, all components it depends on (identify them either by reading documentation or by searching the web), how to make it run.
     You are to provide starter script that sets all necessary environment variables and passes correct flags to Java VM from OpenJDK7 package.
     You are to provide instructions how to test, if the server works (e.g. by providing instructions how to add, search, and remove entries in directory).
     This is research task, there may be no solution, it is possible that you encounter blocking problem. In that case, you are to report steps to reproduce the problem and explanation why you think it is blocking (this certifies as successful task completion too).
     *Tags*: ldap, sso, java
   
   
 ### Outreach/Research  ### Outreach/Research
   
 * **Task: Compare NetBSD with other operating systems of its kind**: NetBSD is an operating system which targets people who like the cleanness of a system, and mostly already have Unix or Linux experience.    * **Task: Compare NetBSD with other operating systems of its kind**: NetBSD is an operating system which targets people who like the cleanness of a system, and mostly already have Unix or Linux experience.  
Line 111  Used tags are (categories are not tagged Line 157  Used tags are (categories are not tagged
   *Tag*: overview    *Tag*: overview
   
 * **Task: Analyze and document (pseudo-)random number generators**: For several purposes like key creation, initial vectors for some protocols, IP sequence numbers, an operating system is required to have a (pseudo) random number generator ((p)rng).    * **Task: Analyze and document (pseudo-)random number generators**: For several purposes like key creation, initial vectors for some protocols, IP sequence numbers, an operating system is required to have a (pseudo) random number generator ((p)rng).  
   Though some are implemented in hardware and the OS gives you the chance to interface them, you most probably just call the function random(3) or open the device /dev/urandom or /dev/random, which is either in hardware or software, depending on what the operating system uses.      Though some are implemented in hardware and the OS gives you the chance to interface them, you most probably just call the function [[!template id=man name="random" section="3"]] or open the device /dev/urandom or /dev/random, which is either in hardware or software, depending on what the operating system uses.  
   While the hardware rngs use some random noise as a source for entropy ("randomness"), software rngs use several sources like disk command execution times, network timing, mouse and keyboard usage, depending on the implementation.      While the hardware rngs use some random noise as a source for entropy ("randomness"), software rngs use several sources like disk command execution times, network timing, mouse and keyboard usage, depending on the implementation.  
   Your task is to look at the prngs of the great Open Source operating systems, analyze how they work, what input they use, how large their pools are and what exactly is done when input or output occurs.      Your task is to look at the prngs of the great Open Source operating systems, analyze how they work, what input they use, how large their pools are and what exactly is done when input or output occurs.  
   This task is once for each operating system which has a different rng (some operating systems share the same ones), but you should analyze the input sources for all OSes using that rng and do the analysis for NetBSD first.      This task is once for each operating system which has a different rng (some operating systems share the same ones), but you should analyze the input sources for all OSes using that rng and do the analysis for NetBSD first.  
Line 120  Used tags are (categories are not tagged Line 166  Used tags are (categories are not tagged
   *Tag*: research      *Tag*: research  
   *Tag*: comparison    *Tag*: comparison
   
   * **Task: Illustrate how to use the framebuffer**: NetBSD features a generic framebuffer framework, called [[!template id=man name="wsfb" section="4"]]. It is already supported by Xorg by the xf86-video-wsfb driver, but it would be nice to investigate other useful ways to use it from userland. This task should illustrate exactly this, explaining and demonstrating how to write pictures on the framebuffer for instance.  
     Note that there is a generic framebuffer implementation for the i386, amd64 and macppc architectures, through the genfb(4) driver; it is known to work on the first two cases with qemu. Some help about how to enable it can be found in [[!template id=man name="boot" section="8"]] (see the "vesa" command). Also, some fixes and improvements to the relevant drivers may only be found in NetBSD-current at the moment.  
     *Prerequisites*: C (basic)  
     *Tag*: research  
     *Tag*: howto  
     *Tag*: system
   
   * **Task: Setup SNMP daemon**: Choose and setup SNMP daemon, describe what one can monitor and control using SNMP.
     *Tag*: research  
     *Tag*: system
     *Tag*: service
     *Tag*: network  
     *Tag*: howto
   
 ### 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 behavior.  * **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.
Line 130  Used tags are (categories are not tagged Line 190  Used tags are (categories are not tagged
   *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, there is not a step-by-step introduction to how configure it.
   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 manpage of [[!template id=man name="npf.conf" section="5"]] gives an introduction, but nothing that could be used as a howto: (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 technical aspects 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](https://www.netbsd.org/~rmind/npf/), this would have to be checked against errors, updated if needed and extended.  
   *Tag*: howto      *Tag*: howto  
   *Tag*: network    *Tag*: network
   
Line 149  Used tags are (categories are not tagged Line 209  Used tags are (categories are not tagged
   *Tag*: ui      *Tag*: ui  
   *Tag*: research    *Tag*: research
   
 * **Task: Document the installation of the DeforaOS desktop environment**: The DeforaOS desktop is an alternative for a lightweight desktop environment, and is already packaged in NetBSD (via pkgsrc-wip, as the wip/deforaos-desktop meta package). It could use more documentation though, including how to configure it properly.  * **Task: Document the installation of the DeforaOS desktop environment**: The DeforaOS desktop is an alternative for a lightweight desktop environment, and is already packaged in NetBSD ([[!template id=pkg category="meta-pkgs" name="deforaos-desktop"]]) and via pkgsrc-wip. It could use more documentation though, including how to configure it properly.
   Bug reports will also be welcome of course, even more so with fixes.    Bug reports will also be welcome of course, even more so with fixes.
   *Tag*: ui    *Tag*: ui
   *Tag*: research    *Tag*: research
Line 161  Used tags are (categories are not tagged Line 221  Used tags are (categories are not tagged
   *Tag*: research    *Tag*: research
   
   
 * **Task: Describe how NetBSD boots**: Build NetBSD on any system (especially non-NetBSD) and try to create a bootable medium without using makefs(8) or integrated wrappers.    * **Task: Describe how NetBSD boots**: Build NetBSD on any system (especially non-NetBSD) and try to create a bootable medium without using [[!template id=man name="makefs" category="8"]] or integrated wrappers.
   Creating a bootable disk is possible, but difficult and there is no comprehensive information about this. You have to try much until you get the real results.      Creating a bootable disk is possible, but difficult and there is no comprehensive information about this. You have to try much until you get the real results.  
   The affected tools are    The affected tools are
   * fdisk(8)    * [[!template id=man name="fdisk" category="8"]]
   * installboot(8)    * [[!template id=man name="installboot" category="8"]]
   * disklabel(8)    * [[!template id=man name="disklabel" category="8"]]
   * gpt(8)    * [[!template id=man name="gpt" category="8"]]
   
   In the end of this task, a small howto and some corrections for the manpages of the affected tools should be there.      In the end of this task, a small howto and some corrections for the manpages of the affected tools should be there.  
   *Tag*: system      *Tag*: system  
   *Tag*: howto    *Tag*: howto
   
   ### Documentation
   
 * **Task: Describe how to boot NetBSD on a gpt disk**: Currently, NetBSD supports booting from a gpt partition, but you cannot know how.    * **Task: Describe how to boot NetBSD on a gpt disk**: Currently, NetBSD supports booting from a gpt partition, but you cannot know how.  
   This task is about creating documentation how to use the tool gpt(8) and maybe installboot(8) how to create GPT labels, how they interact with MBRs as created by fdisk(8), how wedges work on this, and how you would make it bootable.      This task is about creating documentation how to use the tool [[!template id=man name="gpt" section="8"]] and maybe [[!template id=man name="installboot" section="8"]] how to create GPT labels, how they interact with MBRs as created by [[!template id=man name="fdisk" category="8"]], how wedges work on this, and how you would make it bootable.  
   You should also describe which problems you have and what people might edge on when trying to create a gpt-bootable disk.      You should also describe which problems you have and what people might edge on when trying to create a gpt-bootable disk.  
   *Tag*: howto      *Tag*: howto  
   *Tag*: system    *Tag*: system
   
   
 ### Documentation  
   
 * **Task: Howto: Install additional software in NetBSD**: With NetBSD, you have three major ways to install additional software: pkgsrc, pkg_add and pkgin.    * **Task: Howto: Install additional software in NetBSD**: With NetBSD, you have three major ways to install additional software: pkgsrc, pkg_add and pkgin.  
   Which one is to use for which use case, what are their benefits, their merits? Document them, and give a small introduction of the needed tools and their usage (package installation, package deletion, package information).      Which one is to use for which use case, what are their benefits, their merits? Document them, and give a small introduction of the needed tools and their usage (package installation, package deletion, package information).  
   *Tag*: howto      *Tag*: howto  
   *Tag*: system      *Tag*: system  
   *Tag*: service    *Tag*: service
   
 * **Task: Howto: Encrypt the hard disk with NetBSD**: NetBSD has its very nice cryptographic device driver cgd. Apart from being already described in the [guide](http://netbsd.org/docs/guide/en/chap-cgd.html).    * **Task: Howto: Encrypt the hard disk with NetBSD**: NetBSD has its very nice cryptographic device driver [[!template id=man name="cgd" category="4"]]. Apart from being already described in the [guide](http://netbsd.org/docs/guide/en/chap-cgd.html).  
   An explicit howto how to do this (in short) and how to do this during the installation, is the issue of this task.      An explicit howto how to do this (in short) and how to do this during the installation, is the issue of this task.  
   Though cgd will be in sysinst for the next version of NetBSD, the current ones are still without, so there should be a special emphasis of how to add cgd during system installation.      Though cgd will be in sysinst for the next version of NetBSD, the current ones are still without, so there should be a special emphasis of how to add cgd during system installation.  
     Note that support for full-disk encryption has been introduced in NetBSD-current, in the form of a ramdisk (cgdroot.kmod). It still lacks official documentation at the moment, but was detailed [on the mailing-lists](http://mail-index.netbsd.org/current-users/2013/03/thread2.html#022311).  
   *Tag*: howto      *Tag*: howto  
   *Tag*: system    *Tag*: system
   
Line 211  Used tags are (categories are not tagged Line 272  Used tags are (categories are not tagged
   *Tag*: network      *Tag*: network  
   *Tag*: service    *Tag*: service
   
 * **Task: Describe how to backup NetBSD**: Though NetBSD is much like other Unixes in this respect, backup is still something you should consider specially for every operating system. Which tools are available in the base distribution for backupping, like dump(8) and restore(8)?    * **Task: Describe how to backup NetBSD**: Though NetBSD is much like other Unixes in this respect, backup is still something you should consider specially for every operating system. Which tools are available in the base distribution for backupping, like [[!template id=man name="dump" section="8"]] and [[!template id=man name="restore" section="8"]]?  
   Which one suits better, pax(1), dump(8) or even just rsync or other special backup solutions? What are their use cases?      Which one suits better, [[!template id=man name="pax" section="1"]], [[!template id=man name="dump" section="8"]] or even just rsync or other special backup solutions? What are their use cases?  
   What is a full, a differential, an incremental backup? What is the estimated space usage of them, depending on the backups?      What is a full, a differential, an incremental backup? What is the estimated space usage of them, depending on the backups?  
   How would you restore your system after a crash, which steps have to be taken to get a working system again?      How would you restore your system after a crash, which steps have to be taken to get a working system again?  
   After reading the resulting article, the reader should be able to decide for a backup scheme and solution and implement it without further research.      After reading the resulting article, the reader should be able to decide for a backup scheme and solution and implement it without further research.  
Line 220  Used tags are (categories are not tagged Line 281  Used tags are (categories are not tagged
   *Tag*: system      *Tag*: system  
   *Tag*: research    *Tag*: research
   
 * **Task: Describe usage of Multicast DNS in NetBSD**: We have the "Multicast and Unicast DNS daemon" (mdnsd(8)) in NetBSD, which can also be activated directly from the installer (which is one of a few chosen services).    * **Task: Describe usage of Multicast DNS in NetBSD**: We have the "Multicast and Unicast DNS daemon" ([[!template id=man name="mdnsd" section="8"]]) in NetBSD, which can also be activated directly from the installer (which is one of a few chosen services).  
   To be really able to use it, you have to know what it is and what you can do with it.      To be really able to use it, you have to know what it is and what you can do with it.  
   So, your task is to research what Multicast DNS (or zeroconf) is, and document which of the features is already usable with NetBSD and which ones can be installed via pkgsrc, which ones are completely missing (but relevant).      So, your task is to research what Multicast DNS (or zeroconf) is, and document which of the features is already usable with NetBSD and which ones can be installed via pkgsrc, which ones are completely missing (but relevant).  
   The mdnsd(8) manpage and the Wikipedia page for zeroconf might be a good start for this.      The [[!template id=man name="mdnsd" section="8"]] manpage and the Wikipedia page for zeroconf might be a good start for this.  
   *Tag*: howto      *Tag*: howto  
   *Tag*: system      *Tag*: system  
   *Tag*: service      *Tag*: service  
   *Tag*: reserach    *Tag*: research
   
 * **Task: Describe how to use NetBSD as an appliance**: NetBSD is often used for appliances, i.e. a small server serving only one single purpose. Though, there are no howtos describing how to set up a single appliance serving only one cause.    * **Task: Describe how to use NetBSD as an appliance**: NetBSD is often used for appliances, i.e. a small server serving only one single purpose. Though, there are no howtos describing how to set up a single appliance serving only one cause.  
   Though these howtos are targeted at creating a single appliance, they can also be used for other purposes.      Though these howtos are targeted at creating a single appliance, they can also be used for other purposes.  
Line 235  Used tags are (categories are not tagged Line 296  Used tags are (categories are not tagged
   * **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).
   * **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.
     * **media server** - also similar to a file server, a media server has extra requirements. Some specific protocols may have to be deployed (UPnP/DLNA) and configured to support some client implementations in particular. Additional features, such as video transcoding, will be worth investigating as well.
   
   Every howto for an appliance is considered a single task.      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.  
Line 246  Used tags are (categories are not tagged Line 308  Used tags are (categories are not tagged
   *Tag*: system      *Tag*: system  
   *Tag*: network    *Tag*: network
   
 * **Task: Write assembly examples for additional architectures**: there is currently a single assembly example in src/share/examples/asm/hello, for the PowerPC architecture. NetBSD works on many more though; these examples are about illustrating how, at the assembly layer. This task to write basic, functional assembly programs on more architectures; each program is one task. Some architectures may support multiple ABIs, and this should also be investigated and documented while writing each example.  * **Task: Write assembly examples for additional architectures**: there is currently a single assembly example in src/share/examples/asm/hello, for the PowerPC architecture. NetBSD works on many more though; these examples are about illustrating how, at the assembly layer. This task to write basic, functional assembly programs on more architectures; each program is one task. Some architectures may support multiple ABIs, and this should also be investigated and documented while writing each example.  
   Note that "hello", the classic "Hello, world!", is not the only possibility to demonstrate basic assembly on any given architecture; the implementation of other programs can be relevant, provided they illustrate more aspects of assembly coding for the target architecture.    Note that "hello", the classic "Hello, world!", is not the only possibility to demonstrate basic assembly on any given architecture; the implementation of other programs can be relevant, provided they illustrate more aspects of assembly coding for the target architecture.  
   *Prerequisites*: assembly     *Prerequisites*: assembly  
   *Tag*: research     *Tag*: research  
   *Tag*: system    *Tag*: system
   
   * **Task: Setup single sign-on (SSO) service using base Heimdal**
     Write in clear terms what needs to be set up for implementing single sign-on service using Kerberos.
     Write step-by-step instructions for configuration of base Heimdal, BIND, OpenPAM, and other components as needed (both, for client and server).
     Provide instructions how to test functionality (steps how to make sure it works).
     Create a network with at least two machines. Make sure that your instructions apply to this configuration to (write separate sections, for client and for server, if needed).
     Provide instructions how to operate this setup (how to add-remove user accounts, to change-reset passwords, and so on).
     You are to make sure that you provide references to documentation for component you used (e.g. man pages, BIND Administrator Reference Manual).
     You are to make sure that you provide step-by-step instructions for what you did.
     You are to illustrate instructions with shell commands and configuration file snippets.
     *Tags*: security, sso, kerberos, documentation, howto
   
   * **Task: Describe how to become a VoIP provider**
     SIP is a protocol used for VoIP communications.
     NetBSD was sometimes tried as a VoIP server, but there has been no howto yet how to do this.
     So, install an Asterisk or FreeSwitch or something else like that and describe how to use NetBSD as a VoIP server.
     *Tags*: howto, service
   
   ### User interface, user experience
   
   * **Task: Redesign interface of [[!template id=man name="disklabel" section="8"]]**
     It should be possible and easy to use [[!template id=man name="disklabel" section="8"]in command-line mode, so that the [[!template id=man name="disklabel" section="8"]] could be scriptable.
     One of examples of better interface is [[!template id=man name="gpt" section="8"]].
     *Tags*: ui, research
   
   * **Task: Redesign interface of [[!template id=man name="fdisk" section="8"]] to make it closer to [[!template id=man name="gpt" section="8"]]**
     It should be possible and easy to use [[!template id=man name="fdisk" section="8"]] in command-line mode, so that the [[!template id=man name="fdisk" section="8"]] could be scriptable.
     One of examples of better interface is [[!template id=man name="gpt" section="8"]].
     *Tags*: ui, research
   
   * **Task: Window manager selection**
     Find out software that helps user to switch between window manager without session restart.
     Provide instructions how to set it up. Describe user experience.
     *Tags*: ui, research
   
   * **Task: analyze trends in community support channels**
     There exist multiple communication channels. They are organized around different technologies (mail, news, WWW, IRC, XMPP) and different patterns of usage (mail/news subscription, forum, wiki).
     The task is to analyze how communities are organized for different projects (for instance, FreeBSD, Gentoo, Fedora, Debian, Ubuntu), how communities solve related technological and social problems (like SPAM), analyze performance of channels.
     *Tags*: ui, research

Removed from v.1.48  
changed lines
  Added in v.1.69


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