1: # Google Code-In (GCI) project ideas
3: ## Introduction
4: For the application for [Google Code-In 2012](http://code.google.com/opensource/gci/2012/index.html), and as a starting point for people who want to start working on NetBSD, here is a list of tasks to be fulfilled.
6: All the tasks should be completable within hours or up to three days. To get an idea of how much a single task should be and what kind of they could be, look at [this page](http://code.google.com/p/google-code-in/wiki/GCIExampleTasks).
8: Even if you don't want to attend the Code-In, you can use this as a starting point. In most cases, the work needs some research in order to be completed. Just write a mail to one of the [mailing lists](http://www.netbsd.org/mailinglists/ you think is suiting (if you don't find any, just pick netbsd-users) and ask for more details.
10: 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/)
12: ## Goals as stated by Google
13: 1. **Code**: Tasks related to writing or refactoring code
14: 1. **Documentation/Training**: Tasks related to creating/editing documents and helping others learn more
15: 1. **Outreach/Research**: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
16: 1. **Quality Assurance**: Tasks related to testing and ensuring code is of high quality
17: 1. **User Interface**: Tasks related to user experience research or user interface design and interaction
20: ## Proposed tasks
22: ### Used tags:
23: If you want to search for a tag, just search this site for "Tag: $TAGNAME".
24: Used tags are (categories are not tagged):
25: * *man* - tasks related to writing on or working with manpages
26: * *network* - tasks related to networking (including firewalls)
27: * *system* - tasks related to the system itself, either kernel or system level things
28: * *service* - tasks involving services running on the system (as compared to *system*)
29: * *overview* - tasks related to getting and documenting an overview
30: * *howto* - tasks involving the creation of a howto
31: * *comparison* - tasks involving the comparison of different solutions
32: * *research* - tasks involving active research by the student
33: * *ui* - tasks involving the user interface (mostly graphical)
34: * *graphics* - tasks related to creating graphics
37: ### Documentation
39: * **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.
40: The file can be seen here: [usermgmt.conf(5)](http://netbsd.gw.com/cgi-bin/man-cgi?usermgmt.conf+5+NetBSD-current)
41: *Tag*: man
42: *Tag*: system
44: * **Task: Create an overview of NetBSD documentation**: NetBSD has a variety of documentation stored everywhere in the web. On the one hand, there's the website with single articles, the NetBSD Guide, the pkgsrc Guide, documentation in /usr/, the NetBSD wiki, some important mailing list posts, manpages, other mdoc documents, something stored inside the code, etc.
45: In an attempt to gather documentation for NetBSD and provide a nicer entry point for beginners, this task is about gathering the points where documentation lies (with the full path), what language it is written in, what it is about (just a rough overview), and how much it is.
46: For the final goal, see [this mailing list post](http://mail-index.netbsd.org/netbsd-docs/2012/09/20/msg000295.html).
47: If you want to do this task, get in touch with us such that we can provide you with basic information where to start.
48: *Tag*: overview
50: * **Task: Howto: How to get a graphical environment on NetBSD**: NetBSD is a very sleek operating system, delivering an X server (and the mandatory twm), but nothing else. As most people don't like twm, they install another graphical environment.
51: But how do you do so?
52: This task is about creating a howto to install graphical environments after the installation. You should provide screenshots or screendumps (when still being on the console) and describe which configuration files have to be modified, which packages should be installed, which are there after the instalation and which can be added afterwards (special editors, etc.), and so on.
53: The package light-desktop should be stressed in this documentation.
54: *Tag*: ui
55: *Tag*: howto
58: * **Task: Create an overview of the NetBSD server layout**: If you're on a NetBSD mirror, after traversing into the tree you'll see various directories that seem to do the same.
59: You have to traverse the directories of a NetBSD server (ftp.netbsd.org might be the best one, as it is *the* reference), find out which directories have which meaning, and document that. In the end, you should think about a good ASCII representation of a directory tree and realize it.
60: *Tag*: research
61: *Tag*: overview
63: * **Task: Create an overview of the NetBSD releases**: As every project with release engineering, it is difficult for a beginner to know which releases are the current ones, how long will a branch be supported, what are the actual branche names and what is the actual change in a minor or in a major version, what about binary compatibility, and where can I get information all in all?
64: This task is about writing a small article explaining the release engineering of NetBSD.
65: *Tag*: research
66: *Tag*: overview
68: * **Task: Create an overview of the NetBSD src layout**: There is the manpage hier(7), which describes the directory layout of a running NetBSD system.
69: To make it easier for beginners to find things inside src, an equivalent document for the sources of NetBSD.
70: Even if you're not fond with mdoc, researching this and gathering the information (e.g. in plain ASCII or markdown) would be a great benefit, and somebody who likes mdoc can then convert it to a system manpage.
71: *Tag*: research
72: *Tag*: overview
74: * **Task: Howto: Update the system from binaries**: There is the new tool written in shell named sysupgrade (to be found in pkgsrc/sysutils/sysupgrade), which updates the system in binaries for you. Though it is nice, you may have reasons to not use it for an update (e.g. non-standard systems, or some components may not change).
75: This is why you should document the single tasks sysupgrade does (and why) and fill it with examples, in the end creating an howto which resembles the work done by sysupgrade.
76: [sysupgrade usage](http://www.netbsd.org/docs/guide/en/chap-upgrading.html)
77: *Tag*: howto
78: *Tag*: research
80: * **Task: Howto: Install additional software in NetBSD**: With NetBSD, you have three major ways to install additional software: pkgsrc, pkg_add and pkgin.
81: 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).
82: *Tag*: howto
83: *Tag*: system
84: *Tag*: service
86: * **Task: Howto: Dual-boot NetBSD**: Having NetBSD not only as the single operating system, even if only for trying, is a common setup.
87: Of course you can dual-boot NetBSD with its internal bootloader as well as with grub and grub2.
88: These possibilities should be documented, and a howto how to dual-boot NetBSD should be created, for any scenario (NetBSD installed before main OS, and main OS installed before NetBSD).
89: *Tag*: howto
90: *Tag*: research
91: *Tag*: system
93: * **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).
94: An explicit howto how to do this (in short) and how to do this during the installation, is the issue of this task.
95: 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.
96: *Tag*: howto
97: *Tag*: system
99: * **Task: Howto: Running usermanagement with LDAP and Kerberos**: Having NetBSD being a server is a common setup. Additionally to all the LDAP and Kerberos setup tutorials in the web, an explicit tutorial how to use NetBSD as an LDAP and Kerberos server would be nice.
100: This means you shouldn't reproduce all the other tutorials about the gory internals, but rather describe what has to be done which is NetBSD-specific (which packages have to be installed, where their configuration files lie, etc.) and just a short chapter about what is needed for the rest, with a reference to the original OpenLDAP and Heimdal/MIT documentation.
101: *Tag*: howto
102: *Tag*: service
103: *Tag*: system
105: * **Task: Howto: Running a webserver with Apache**: As well as the aforementioned task with OpenLDAP and Kerberos, a howto what to do with Apache in NetBSD would be good.
106: This should also include a reference to the already included bozohttpd, which may be suited better in some cases.
107: *Tag*: howto
108: *Tag*: service
109: *Tag*: system
111: * **Task: Howto: Using LVM to manage your disks**: There is already a [chapter about the logical volume manager in NetBSD](http://netbsd.org/docs/guide/en/chap-lvm.html).
112: This task is about not having a whole chapter about it, but rather a small and comprehensive howto how you would manage logical volumes with NetBSD instead of reading through the whole chapter.
113: *Tag*: howto
114: *Tag*: system
116: * **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)).
117: You should write an article that introduces the reader to these systems, how they interact, and what their use cases are.
118: *Tag*: howto
119: *Tag*: system
121: * **Task: Rewrite system configuration in the guide**: January this year, we got a [new configuration menu for the installer](http://mail-index.netbsd.org/tech-install/2012/01/23/msg000223.html)
122: The chapter in the guide about system configuration is still [the old one](http://netbsd.org/docs/guide/en/chap-exinst.html#exinst-system-configuration)
123: Your task is to rewrite this paragraph, add a new screenshot such that it fits the new configuration menu.
124: *Tag*: howto
125: *Tag*: ui
127: * **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.
128: On the way, you could separate obsolete articles from newer ones.
129: 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.
130: *Tag*: wiki
132: * **Task: Convert the NetBSD Guide from DocBook to Markdown**: There are already tools to convert docbook to markdown (e.g. pandoc), so they have to be applied. The results have to be checked whether they are useful, and then every chapter should be a single wiki article, with one overview, such that the user optimally doesn't see the difference between the website and the wiki guide.
133: [The guide](http://www.netbsd.org/docs/guide/en/index.html), [the sources](http://cvsweb.netbsd.org/bsdweb.cgi/htdocs/docs/guide/).
134: *Tag*: wiki
136: * **Task: Convert installation notes to markdown**: Currently, the [installation notes](http://ftp.netbsd.org/pub/NetBSD/NetBSD-5.1.2/i386/INSTALL.html) are constructed with mdoc from distrib/notes.
137: The task is to research whether it is possible to convert these articles to markdown, and, if possible, do so.
138: There might be many inclusions etc. to get the original structure, but even the result of *what* has to be done without the actual conversion would be neat.
139: *Tag*: wiki
140: *Tag*: man
142: * **Task: Describe how to run NetBSD headless**: For any server usage, you want to use NetBSD without access to keyboard, mouse or monitor. For these usages, you want to have access via ssh (or something similar, document that) or serial console.
143: Your task is to describe the steps which are necessary to run a NetBSD system headless, i.e. printing boot messages to serial port, enabling the bootloader on serial, enabling the serial port, describing the possible options how to do so, which security measures should be taken.
144: You should also consider systems which don't even have a serial port, i.e. what has to be done if you cannot watch a device start, but you *must* go sure it will come up and you have some sort of access (like a router).
145: *Tag*: howto
146: *Tag*: system
148: * **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.
149: 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).
150: *Tag*: howto
151: *Tag*: system
152: *Tag*: network
153: *Tag*: service
155: * **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.
156: Though these howtos are targeted at creating a single appliance, they can also be used for other purposes.
157: Possible appliances would be:
158: * **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
159: * **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).
160: Every howto for an appliance is considered a single task.
161: * **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.
162: 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.
163: 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.
164: *Prerequisites*: sh
165: *Tag*: howto
166: *Tag*: research
167: *Tag*: service
168: *Tag*: system
169: *Tag*: network
171: * **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)?
172: Which one suits better, pax(1), dump(8) or even just rsync or other special backup solutions? What are their use cases?
173: What is a full, a differential, an incremental backup? What is the estimated space usage of them, depending on the backups?
174: How would you restore your system after a crash, which steps have to be taken to get a working system again?
175: After reading the resulting article, the reader should be able to decide for a backup scheme and solution and implement it without further research.
176: *Tag*: howto
177: *Tag*: system
178: *Tag*: research
180: * **Task: Describe how to create a NetBSD live flash drive**: Flash drives become increasingly the source for operating system installations.
181: Though, you might want to try the operating system first by using a live system.
182: In this task you should create a live USB flash drive from NetBSD. You can use Jibbed or the installation USB flash drive images as an example how to do this.
183: In the end, there should be a howto which steps have to be taken to enable NetBSD to boot from a flash drive.
184: *Tag*: howto
185: *Tag*: research
186: *Tag*: system
188: * **Task: Describe how to become a voip provider**: Sip is a protocol used for VoIP communications.
189: NetBSD was sometimes tried as a VoIP server, but there has been no howto yet how to do this.
190: So, install an Asterisk or FreeSwitch or something else like that and describe how to use NetBSD as a VoIP server.
191: *Tag*: howto
192: *Tag*: service
195: ### Outreach/Research
197: * **Task: Howto: Getting in touch with NetBSD**: If you have a problem, there are several ways to get in touch with NetBSD people: BSD user groups, mailing lists, IRC, problem reports... Which one is the best for which issue?
198: Document the single methods for contacting others and categorize them by the task they're useful for.
199: *Tag*: howto
200: *Tag*: research
201: *Tag*: overview
203: * **Task: Compare init systems with each other**: Additional to the historical ones (SysV and BSD), systemd recently added another init system to the Unix world.
204: An objective comparison of these three systems (if there are other major ones, add them, maybe upstart?) would be nice. Not in the sense of showing their features side-by-side, but simply describing how they work and how you do things yourself.
205: In the end, you should have created a small article that enables anyone using one of these systems to switch to the other one just by reading this article.
206: *Tag*: comparison
207: *Tag*: research
208: *Tag*: system
210: * **Task: Investigate and document Markdown to PDF and text conversion**: Propose a method for converting NetBSD Guide Markdown pages into PDF and text, so that they can be delivered with releases. Note the information (description, source location, home page, build method) so that a pkgsrc package (or packages) can be built using the proposed tools (the tools chosen must be compilable for NetBSD, and other free Unix-like systems).
211: *Tag*: research
212: *Tag*: overview
214: * **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.
215: 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.
216: 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.
217: 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.
218: 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.
219: *Tag*: comparison
220: *Tag*: research
221: *Tag*: system
222: *Tag*: overview
224: * **Task: Analyze NetBSD's users**: NetBSD is a very universal operating system. Some people run it on their 20 years old VAXen, others on their recent desktop computer or server, or on their tiny ARM box as a router.
225: As the aforementioned task (which is rather about the others out there), this task is about doing an in-depth analyzation of NetBSD itself. What kind of users and what kind of developers are out there? Look at the mailing lists to get an impression about the community and the developers and what their goals are.
226: This task is also about thinking about some statistical methods you could use. What data is available you could easily analyze, what are the metrics? Do other distributions have the same data available, so you could eventually run these statistics on other operating systems?
227: This task does not have to be about analyzation, but could also be simply the research how you could do this, which statistical methods. Maybe the student is not able to do the actual computation because of a lack of sources and computing power.
228: Besides being a gci task, thinking about these statistics, you could also create a nice website analyzing distributions based on statistical methods.
229: *Tag*: research
230: *Tag*: comparison
231: *Tag*: system
232: *Tag*: overview
234: * **Task: Compare firewall solutions in NetBSD**: NetBSD has several firewall solutions on board: ipf, npf, pf, even more (you should research that).
235: For the beginner, it is not clear what they are capable of, how fast they are and what their syntaxes look like.
236: 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.
237: *Tag*: comparison
238: *Tag*: network
239: *Tag*: research
242: ### Quality Assurance
244: * **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.
245: The goal is to create a comprehensive (!) list of full software packages that are already included in the base distribution.
246: 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.
247: *Tag*: overview
248: *Tag*: research
250: * **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.
251: 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.
252: This also includes bug-checking for light-deskop, the preferred package for a NetBSD desktop.
253: *Tag*: ui
254: *Tag*: research
256: * **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.
257: Ideally, create a pkgsrc meta package including all the dependencies.
258: Report bugs you find on the way.
259: *Tag*: ui
260: *Tag*: research
262: * **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.
263: 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.
264: As testing is an endless task, here are just a few ideas about which items could be tested:
265: * [[!template id=man name="atomic_ops" section="3"]]
266: * [[!template id=man name="cdbr" section="3"]] and [[!template id=man name="cdbw" section="3"]]
267: * [[!template id=man name="inet" section="3"]] and [[!template id=man name="inet_net" section="3"]]
268: * [[!template id=man name="ethers" section="3"]], [[!template id=man name="iso_addr" section="3"]] and [[!template id=man name="link_addr" section="3"]]
269: * [[!template id=man name="strtol" section="3"]], [[!template id=man name="strtoul" section="3"]] and [[!template id=man name="strtoull" section="3"]]
270: * [[!template id=man name="uuid" section="3"]]
271: 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.
272: The tests should be written in either C or sh.
273: *Prerequisites*: sh or C
274: *Tag*: man
275: *Tag*: research
277: * **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.
278: 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.
279: The affected tools are
280: * fdisk(8)
281: * installboot(8)
282: * disklabel(8)
283: * gpt(8)
284: In the end of this task, a small howto and some corrections for the manpages of the affected tools should be there.
285: *Tag*: system
286: *Tag*: howto
288: * **Task: Describe how to boot NetBSD on a gpt disk**: Currently, NetBSD supports booting from a gpt partition, but you cannot know how.
289: 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.
290: You should also describe which problems you have and what people might edge on when trying to create a gpt-bootable disk.
291: *Tag*: howto
292: *Tag*: system
294: * **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.
295: 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).
296: 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.
297: 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.
298: *Tag*: howto
299: *Tag*: network
302: ### Code
304: * **Task: Document different time structures**: We have several time structures like `time_t`, `struct timespec`, `struct timeval`, `struct tm` and so on. Document all of them as a time(5) manpage such that a programmer can see all of them at once, in comparison. As we have time zone sensitive and time zone independent representations, figuring out conversions between local time and UTC from manual pages is hard and should also be documented in that manpage.
305: *Prerequisites*: C coding skills (just reading)
306: *Tag*: man
307: *Tag*: system
309: * **Task: Add an web interface to apropos**: Last year's Google Summer Of Code project was creating a new apropos(1). Though the current version already has a web interface, adding CSS and appropriate HTML to the web interface would be nice to integrate it to other websites.
310: Though the source code is written in C, C knowledge is not necessary. You just have to extract the HTML and pseudo-understand what the code around it does, i.e. in which cases the single actions are taken.
311: The file which would be modified is [apropos-utils.c](https://github.com/abhinav-upadhyay/apropos_replacement/tree/cgi).
312: *Prerequisites*: C CSS HTML
313: *Tag*: ui
314: *Tag*: graphics
316: * **Task: Create a pkgsrc package to get the wiki offline**: The NetBSD wiki can be fetched via cvs or rsync. As it is going to be filled up with information, you might want to have it offline.
317: The goal of this task is to create a pkgsrc package which depends on the tools necessary for offline-viewing of the wiki (this could also be just the integrated if you consider Markdown readable enough) and fetches the wiki.
318: All in all a simple package with few dependencies if any and one or two wrapper scripts.
319: *Prerequisites*: C or sh
320: *Tag*: wiki
321: *Tag*: research
323: * **Task: Describe all MK* variables**: Describe all the MK* variables and how they affect the builds.
324: Suggest improvements or removal.
325: *Tag*: research
327: * **Task: Write apropos branch to search through markdown**: apropos(1) is a last summer's Google Summer Of Code project implemented in NetBSD. It allows a relevance-based search through manpages.
328: 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.
329: 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).
330: 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.
331: [http://mail-index.netbsd.org/tech-userlevel/2012/02/01/msg006040.html](Mail announcing import of apropos)
332: *Prerequisites*: C
333: *Tag*: research
334: *Tag*: man
336: * **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.
337: 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.
338: 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".
339: 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.
340: 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.
341: The prerequisites are only for the coding part.
342: [http://fossil.instinctive.eu/libsoldout/index](libsoldout, a public-domain Markdown implementation in C)
343: *Prerequisites*: C or sh
344: *Tag*: research
345: *Tag*: wiki
348: ### User Interface
350: * **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.
351: If you're fine with drawing on a computer or graphical programs (like The Gimp or Photoshop), this might be a nice and very creative task for you.
352: *Tag*: graphics
354: * **Task: Create an icon set for NetBSD - research**: To provide a nice graphical user interface, as well as prettifying the wiki and the website, having some buttons and icons would be nice.
355: This task is about gathering and writing down what sizes are useful, and what kinds of icons are needed (and what they could be used for).
356: *Tag*: research
357: *Tag*: ui
359: * **Task: Create an icon set for NetBSD - graphics**: In addition to the previous task, creating those icons is still needed. You would have to think about an artwork concept, how these icons should look overall and creating the single icons that are specified.
360: This task could be fulfilled multiple times, and if you succeed well, it would be nice if we could stay in touch with you about this in the future (like adding further graphics).
361: *Tag*: graphics
362: *Tag*: ui
364: * **Task: Create smaller NetBSD artwork**: NetBSD does not have much artwork. Except from the aforementioned wallpapers and icons sets, multiple smaller artworks would be nice as well.
365: This includes drawing comics, creating a CD label, the image of a flash drive with NetBSD on it or e.g. a Beastie with a NetBSD flash drive, such things.
366: If you want to do this task, even if you don't know what to do, just contact us. We can tell you some ideas what to do, and if you already have one, approve it is suited for us.
367: *Tag*: graphics
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb