1. Explanation

A code bounty is a certain financial stimulant to encourage someone to put his or her effort into a project. A code bounty in the DragonFlyBSD project needs to adhere to a set of rules defined hereunder, though these are only preliminary and subject to change. One could for example imagine developers accepting sponsorship on a wholly different basis, or non-financial rewards for completing a bounty project, like free hardware (we love that!).

2. Rules

Bounty Projects are open to anyone that has a reasonable capability of completing the project. Typically it's on first to ask basis, but the sponsor of the bounty may choose differently.
If the developer can not complete the project by the given time period, the bounty agreement is void and no money will be issued for work done. DragonFly developers may extend the time period if it's reasonable and prudent to do so. Upon voiding the agreement, someone may reissue the project again to another developer.
Payment for a project shall be issued in no less then 72 hours after the DragonFly developers has had ten business days to determine if the code is stable and usefulness, no major issues are left unresolved and able for being merged into the project. Payment shall be in either Paypal (preferred), some money sending company or a bank account transfer.
Upon recieving payment, the project developer shall issue (within 24 hours) a message in the WIKI and to DragonFly development ML that they have recieved payment.
All code submitted shall be of the same license as DragonFly. Any questions on the licensing issues should directed to the DragonFly Team.

3. List of bounties

3.1. UTF-8 support in Console

3.1.1. Description

Adding full UTF-8 support in console.

3.1.2. Technical details

Not yet written.

3.1.3. Main goals

Not yet written.

3.1.4. Estimated time

Still unknown.

3.1.5. Donators

timofonic: 35 eur.

TOTAL AMOUNT 35 eur.

3.2. Linux emu update

3.2.1. Description

Port FreeBSD's linux emu to DragonFly and replace ours with it. Preferably linux emu from FreeBSD-current should be used so that we can easily (well, at least easier) sync the linuxulator again. More information on freebsd's linux emu can be found at: http://wiki.freebsd.org/linux-kernel

3.2.2. Technical details

Not yet written.

3.2.3. Main goals

Not yet written.

3.2.4. Estimated time

No set date, just the sooner the better.

3.2.5. Donators

Rumko: 150 EUR
Hasso: 100 EUR

TOTAL AMOUNT 250 EUR

3.3. nataraid update and ICH6R

3.3.1. Description

Our nataraid hasn't been updated in a while. It would be nice to update our nataraid to FreeBSD's latest ataraid. It would be nice to also take care of some freebsd's PRs (kern/108924, kern/102211, kern/102210 and kern/121899).

3.3.2. Technical details

Not yet written.

3.3.3. Main goals

Have a new(er) machine that has ICH6R on-board RAID. If an array is created in the RAID's configuration utility, dfly does not recognise it. If the array is created with natacontrol, the configuration utility doesn't properly recognise it (when trying to manage arrays, it outputs that there are no arrays, while trying to create an array outputs that there are no free drives). When the bounty will be completed, ICH6R must work with dfly. Dfly has to recognise the array and have the ability to properly create/delete it.
Some testing can be done by me (look for Rumko on #dragonflybsd on EFNet) ... I'd prefer if an ISO with /boot.config with -h and ttyd0 turned on would be supplied, but even patches would be accepted.

3.3.4. Estimated time

By the end of next week (11th July), since it should be just updating (according to the commits in FreeBSD, latest ataraid should work with ICH6R?), it shouldn't take so much time?

3.3.5. Donators

Rumko: 75 EUR

TOTAL AMOUNT 75 EUR