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

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.

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.

* kerma *: 100 usd.

TOTAL AMOUNT 35 eur + 50 + 100 usd.

Bring in usb4bsd

Description

Completely rip out our usb stack and replace it with FreeBSD's new usb4bsd (or whatever the FreeBSD-current USB stack is called nowadays).

Note that some work was done here already by polachok (http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/shortlog/refs/heads/usb2) but the state is unknown.

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)

Compress blocks as they get written to disk.

Only file data (rec_type == DATA) should be compressed, not meta-data.

the CRC should be that of the uncompressed data.

ideally you'd need to associate the uncompressed data with the buffer cache buffer somehow, so that decompression is only performed once.

compression could be turned on a per-file or per-pfs basis.

gzip compression would be just fine at first; lzo or lzjb might be preferable.

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