DragonFly BSD

Code Bounties

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!).

Rules

List of bounties

UTF-8 support in Console

Description

Adding full UTF-8 support in console.

Technical details

Not yet written.

Main goals

Not yet written.

Estimated time

Still unknown.

Donators

* timofonic *: 35 eur.

* Dillon *: 50 usd.


TOTAL AMOUNT 35 eur + 50 usd.


Bring in usb4bsd

Description

Technical details

Not yet written.

Main goals

Not yet written.

Estimated time

Unknown.

Donators

* alexh *: 300 usd.

* sjg *: 100 usd.

* ferz *: 50 eur. (already paid)

* tuxillo *: 50 eur


TOTAL AMOUNT 400 usd + 100 eur


Port valgrind to DragonFlyBSD

Description

(shamelessly copied from gsoc2010 projects page)

Valgrind is a very useful tool on a system like DragonFly that's under heavy development. Ideally, we would want the port to be usable with vkernel processes, thus enabling complex checking of the core kernel code.

Technical details

Not yet written.

Main goals

(shamelessly copied from gsoc2010 projects page)

The goal of this project is to port valgrind (3.5.0+) to the DragonFlyBSD platform so that at least the memcheck tool runs sufficiently well to be useful. Also an update for the pkgsrc package (devel/valgrind) should be made.

Estimated time

Unknown.

Donators

* Rumko *: 100 eur.

* tuxillo *: 50 eur.

* Dillon *: 100 usd.

* sjg *: 50 usd.


TOTAL AMOUNT 150 eur + 150 usd.


HAMMER compression

Description

(shamelessly copied from gsoc2010 projects page)

Technical details

(shamelessly copied from gsoc2010 projects page)

Doing compression would require flagging the data record as being compressed and also require double-buffering since the buffer cache buffer associated with the uncompressed data might have holes in it and otherwise referenced by user programs and cannot serve as a buffer for in-place compression or decompression.

The direct read / direct write mechanic would almost certainly have to be disabled for compressed buffers and the small-data zone would probably have to be used (the large-data zone is designed only for use with 16K or 64K buffers).

Main goals

Not yet written.

Estimated time

Unknown.

Donators

* Rumko *: 50 eur.

* Dillon *: 100 usd.

* vsrinivas *: 50 usd.


TOTAL AMOUNT 50 eur + 150 usd.