5: # Google Code-In (GCI)
7: Google Code-In is a project like Google Summer Of Code. But this time, there are
8: not university students, but 13-18 years old people the targeted audience.
9: Previous Code-In organisations:
11: * [Code-In 2010](http://www.google-melange.com/gci/accepted_orgs/google/gci2010)
12: * [Code-In 2011](http://www.google-melange.com/gci/accepted_orgs/google/gci2011)
13: * [Code-In 2012](http://www.google-melange.com/gci/accepted_orgs/google/gci2012)
15: Code-In differs from Summer Of Code also in not having a single task for one
16: student, but creating a large number of tasks and then having the students pick
17: the ones they want to work on. Thus, it is not suited for large projects, but
18: for small tasks like writing howtos, fixing bugs.
20: All the tasks should be completable within hours or up to three days. To get an
21: idea of how much a single task should be and what kind of they could be, look
22: at [this page](http://code.google.com/p/google-code-in/wiki/GCIExampleTasks).
23: There is [information from Google]
24: (http://code.google.com/p/google-code-in/wiki/GCIMentorInformation2012) about
25: what is suitable as a task for Code-In.
27: **NetBSD participated in Code-In 2012.** You can find the results
28: [[here|code-in_2012]]. The status of integrating Code-In's work to NetBSD can
29: also be read there.
31: ## Goals as stated by Google
32: 1. **Code**: Tasks related to writing or refactoring code
33: 1. **Documentation/Training**: Tasks related to creating/editing documents and
34: helping others learn more
35: 1. **Outreach/Research**: Tasks related to community management,
36: outreach/marketing, or studying problems and recommending solutions
37: 1. **Quality Assurance**: Tasks related to testing and ensuring code is of high
39: 1. **User Interface**: Tasks related to user experience research or user
40: interface design and interaction
42: ## Tasks
44: There were some tasks left, and there might be more ideas over the following
45: year to participate in Code-In 2017 again.
47: ## Used tags
48: If you want to search for a tag, just search this site for "Tag: $TAGNAME".
49: Used tags are (categories are not tagged):
51: * *man* - tasks related to writing on or working with manpages
52: * *network* - tasks related to networking (including firewalls)
53: * *system* - tasks related to the system itself, either kernel or system level
55: * *service* - tasks involving services running on the system (as compared to
57: * *overview* - tasks related to getting and documenting an overview
58: * *howto* - tasks involving the creation of a howto
59: * *comparison* - tasks involving the comparison of different solutions
60: * *research* - tasks involving active research by the student
61: * *ui* - tasks involving the user interface (mostly graphical)
62: * *graphics* - tasks related to creating graphics
64: ## Tasks
66: ### Code
68: * **Task: Serve HTML man pages using NetBSD's "bozohttpd" server**
69: 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
70: 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
71: name of a man page can be entered (see [[!template id=man name="httpd" section="8"]]).
72: When the form is submitted, the Lua script will do a lookup if there is a corresponding
73: man page in html form and deliver to the web-browser. Contact mbalmer@ if you have questions.
74: *Prerequisites*: Lua, HTML.
75: *Tag*: man
76: *Tag*: service
77: *Tag*: ui
79: * **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.
80: 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.
81: As testing is an endless task, here are just a few ideas about which items could be tested:
82: * [[!template id=man name="atomic_ops" section="3"]]
83: * [[!template id=man name="cdbr" section="3"]] and [[!template id=man name="cdbw" section="3"]]
84: * [[!template id=man name="inet" section="3"]] and [[!template id=man name="inet_net" section="3"]]
85: * [[!template id=man name="ethers" section="3"]], [[!template id=man name="iso_addr" section="3"]] and [[!template id=man name="link_addr" section="3"]]
86: * [[!template id=man name="strtol" section="3"]], [[!template id=man name="strtoul" section="3"]] and [[!template id=man name="strtoull" section="3"]]
87: * [[!template id=man name="uuid" section="3"]]
89: Though this task is originally rather considered quality assurance, the actual test writing is only coding work (whether the test succeeds or not, is up to the original author of the library or tool).
90: Every *single written test* is considered as **one task**. If you think there is another test that should be added, but is not listed here, feel free to contact us.
91: The tests should be written in either C or sh, depending on the test subject.
92: *Prerequisites*: sh or C
93: *Tag*: man
94: *Tag*: research
96: * **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.
97: 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).
98: For each software package there are three formal tasks of different complexity (unless noted):
99: * make draft package that passes configure phase (medium complexity);
100: * make draft package that passes build phase (medium complexity);
101: * complete package that passes packaging checks and creates binary package (easy).
102: *Tags*: code, pkgsrc
104: * **Task: Avoiding TeX dependencies for [[!template id=pkg category="meta-pkgs" name="netbsd-www"]]**
105: It has been reported that one of obstacles when maintaining NetBSD documentation is the cost of update of tool packages.
106: 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).
107: 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.
108: *Tags*: code, pkgsrc
110: * **Task: Search engine (Lucene)**
111: Status: Reopened Time to complete: 96 hrs Mentors: Radoslaw Kujawa, Aleksej Saushev Tags:
112: 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.
113: 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.
114: Provide instructions how to deploy Lucene itself and all needed components, if it isn't done automatically already.
115: Provide instructions how to setup and test functionality.
116: If possible, automate everything you can.
117: 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.
118: It is possible that some things are not essential to setup. Clear explanation why some requirement is not met is accepted.
119: In case you have further questions when working on the task, don't hesitate to contact us on #netbsd-code.
120: *Tags*: desktop, web, java, pkgsrc, code
122: * **Task: Make ApacheDS run on NetBSD**
123: 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.
124: 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.
125: You are to provide starter script that sets all necessary environment variables and passes correct flags to Java VM from OpenJDK7 package.
126: 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).
127: 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).
128: *Tags*: ldap, sso, java
131: ### Outreach/Research
133: * **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.
134: As such, there are other operating systems which fall into the same audience as NetBSD does, which are at least Slackware, Arch Linux, Gentoo, OpenBSD, FreeBSD, DragonFly.
135: This task is about researching what other distros are out there which are close to NetBSD's principles and use cases (distrowatch.org might be a good starting point), and how they are different.
136: After having collected facts, maybe a simple overview of the community (what kind of people are there, what do they want?), you should create an article which lists all those and describes their differences to NetBSD.
137: You could also try interviewing some people what their view of the communities and the operating systems is and try to evolve your own opinion about them all.
138: *Tag*: comparison
139: *Tag*: research
140: *Tag*: system
141: *Tag*: overview
143: * **Task: Compare firewall solutions in NetBSD**: NetBSD has several firewall solutions on board: ipf, npf, pf, even more (you should research that).
144: For the beginner, it is not clear what they are capable of, how fast they are and what their syntaxes look like.
145: In this task you should research the differences of these firewalls, create some examples that do the same (so you can view them side-by-side) and provide links to further documentation.
146: *Tag*: comparison
147: *Tag*: network
148: *Tag*: research
150: * **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.
151: 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.
152: 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.
153: In the end, you should write a paper with the results of the survey and a small text, at least one page at all.
154: This task can be fulfilled multiple times, once for each project.
155: *Projects*: FreeBSD, OpenBSD, DragonFly, Gentoo, Slackware, PostgreSQL
156: *Tag*: research
157: *Tag*: comparison
158: *Tag*: overview
160: * **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).
161: 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.
162: 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.
163: 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.
164: 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.
165: You should write down your result in a paper at least two pages long.
166: While this task might take up more work than a usual task, it is a very interesting and demanding task especially if you are interested in mathematics or cryptography.
167: *Tag*: research
168: *Tag*: comparison
170: * **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.
171: 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.
172: *Prerequisites*: C (basic)
173: *Tag*: research
174: *Tag*: howto
175: *Tag*: system
177: * **Task: Setup SNMP daemon**: Choose and setup SNMP daemon, describe what one can monitor and control using SNMP.
178: *Tag*: research
179: *Tag*: system
180: *Tag*: service
181: *Tag*: network
182: *Tag*: howto
184: ### Quality Assurance
186: * **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.
187: 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.
188: You should then insert this part into a list and document whether it complies to POSIX and if not, which differences are there.
189: 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.
190: The prerequisite is only for looking at libraries.
191: *Prerequisite*: C (reading)
192: *Tag*: research
194: * **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.
195: 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.
196: 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.
197: 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.
198: *Tag*: howto
199: *Tag*: network
201: * **Task: Document integrated tools in NetBSD**: Apart from the famous web server and ftp server choices, there are smaller ones already integrated to NetBSD, as well as other smaller tools a user should know.
202: The goal is to create a comprehensive (!) list of full software packages that are already included in the base distribution.
203: In the document src/doc/3RDPARTY there is already a list of imported software, but there are more tools which are NetBSD-inherent themselves or contained in a larger package that is just listed as a whole there.
204: *Tag*: overview
205: *Tag*: research
207: * **Task: Try out various desktop scenarios, report errors**: Modern desktop environments like Xfce, KDE, Gnome or LXDE are mostly written for Linux. As such, it is important to try them on NetBSD and report their errors. Plus, checking the ease of installation via pkgsrc - which packages have to be installed, how intuitive is their name, their installation? Everything should be as easy as possible.
208: This task also refers to the task of creating a tutorial - maybe doing this first, and then creating the tutorial would be nice. The tutorial could either be updated on the fly when the reported bugs are corrected, or will be held back until the process is as easy as it should be.
209: This also includes bug-checking for light-deskop, the preferred package for a NetBSD desktop.
210: *Tag*: ui
211: *Tag*: research
213: * **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.
214: Bug reports will also be welcome of course, even more so with fixes.
215: *Tag*: ui
216: *Tag*: research
218: * **Task: Make NetBSD a music or video player**: NetBSD could as well serve as a music (mpd) or video player. You have to research which packages are needed for such a use case, and document it in a tutorial.
219: Ideally, create a pkgsrc meta package including all the dependencies.
220: Report bugs you find on the way.
221: *Tag*: ui
222: *Tag*: research
225: * **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.
226: 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.
227: The affected tools are
228: * [[!template id=man name="fdisk" category="8"]]
229: * [[!template id=man name="installboot" category="8"]]
230: * [[!template id=man name="disklabel" category="8"]]
231: * [[!template id=man name="gpt" category="8"]]
233: In the end of this task, a small howto and some corrections for the manpages of the affected tools should be there.
234: *Tag*: system
235: *Tag*: howto
237: ### Documentation
239: * **Task: Describe how to boot NetBSD on a gpt disk**: Currently, NetBSD supports booting from a gpt partition, but you cannot know how.
240: 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.
241: You should also describe which problems you have and what people might edge on when trying to create a gpt-bootable disk.
242: *Tag*: howto
243: *Tag*: system
246: * **Task: Howto: Install additional software in NetBSD**: With NetBSD, you have three major ways to install additional software: pkgsrc, pkg_add and pkgin.
247: 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).
248: *Tag*: howto
249: *Tag*: system
250: *Tag*: service
252: * **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).
253: An explicit howto how to do this (in short) and how to do this during the installation, is the issue of this task.
254: 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.
255: 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).
256: *Tag*: howto
257: *Tag*: system
259: * **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.
260: 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.
261: *Tag*: howto
262: *Tag*: system
264: * **Task: Convert articles from the website to wiki articles**: There are several articles on the website (like [this one](http://netbsd.org/docs/misc/index.html)) which should be converted to wiki articles.
265: On the way, you could separate obsolete articles from newer ones.
266: Though this work could also partially be done by a tool like pandoc, the articles on the website have different format: Sometimes docbook, sometimes html, sometimes a mix of them. And pandoc doesn't result in such good results as hand-conversion might do.
267: *Tag*: wiki
269: * **Task: Describe how to use NetBSD as a bluetooth access point**: With bluetooth, you can easily connect your computer to a mobile phone and let the phone use the network connection of the computer.
270: Your task is to describe how to do this: Connecting NetBSD via bluetooth to your phone and then provide different services (especially file transfer and network connection).
271: *Tag*: howto
272: *Tag*: system
273: *Tag*: network
274: *Tag*: service
276: * **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"]]?
277: 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?
278: What is a full, a differential, an incremental backup? What is the estimated space usage of them, depending on the backups?
279: How would you restore your system after a crash, which steps have to be taken to get a working system again?
280: After reading the resulting article, the reader should be able to decide for a backup scheme and solution and implement it without further research.
281: *Tag*: howto
282: *Tag*: system
283: *Tag*: research
285: * **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).
286: To be really able to use it, you have to know what it is and what you can do with it.
287: 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).
288: The [[!template id=man name="mdnsd" section="8"]] manpage and the Wikipedia page for zeroconf might be a good start for this.
289: *Tag*: howto
290: *Tag*: system
291: *Tag*: service
292: *Tag*: research
294: * **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.
295: Though these howtos are targeted at creating a single appliance, they can also be used for other purposes.
296: Possible appliances would be:
297: * **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
298: * **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).
299: * **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.
300: * **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.
302: Every howto for an appliance is considered a single task.
303: 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.
304: 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.
305: *Prerequisites*: sh
306: *Tag*: howto
307: *Tag*: research
308: *Tag*: service
309: *Tag*: system
310: *Tag*: network
312: * **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.
313: 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.
314: *Prerequisites*: assembly
315: *Tag*: research
316: *Tag*: system
318: * **Task: Setup single sign-on (SSO) service using base Heimdal**
319: Write in clear terms what needs to be set up for implementing single sign-on service using Kerberos.
320: Write step-by-step instructions for configuration of base Heimdal, BIND, OpenPAM, and other components as needed (both, for client and server).
321: Provide instructions how to test functionality (steps how to make sure it works).
322: 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).
323: Provide instructions how to operate this setup (how to add-remove user accounts, to change-reset passwords, and so on).
324: You are to make sure that you provide references to documentation for component you used (e.g. man pages, BIND Administrator Reference Manual).
325: You are to make sure that you provide step-by-step instructions for what you did.
326: You are to illustrate instructions with shell commands and configuration file snippets.
327: *Tags*: security, sso, kerberos, documentation, howto
329: * **Task: Describe how to become a VoIP provider**
330: SIP is a protocol used for VoIP communications.
331: NetBSD was sometimes tried as a VoIP server, but there has been no howto yet how to do this.
332: So, install an Asterisk or FreeSwitch or something else like that and describe how to use NetBSD as a VoIP server.
333: *Tags*: howto, service
335: ### User interface, user experience
337: * **Task: Redesign interface of [[!template id=man name="disklabel" section="8"]]**
338: 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.
339: One of examples of better interface is [[!template id=man name="gpt" section="8"]].
340: *Tags*: ui, research
342: * **Task: Redesign interface of [[!template id=man name="fdisk" section="8"]] to make it closer to [[!template id=man name="gpt" section="8"]]**
343: 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.
344: One of examples of better interface is [[!template id=man name="gpt" section="8"]].
345: *Tags*: ui, research
347: * **Task: Window manager selection**
348: Find out software that helps user to switch between window manager without session restart.
349: Provide instructions how to set it up. Describe user experience.
350: *Tags*: ui, research
352: * **Task: analyze trends in community support channels**
353: 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).
354: 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.
355: *Tags*: ui, research
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb