5 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!).
9 * 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.
11 * 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.
13 * Payment for a project shall be issued in no less than 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.
15 * Upon receiving payment, the project developer shall issue (within 24 hours) a message in the WIKI and to DragonFly development ML that they have received payment.
17 * All code submitted shall be of the same license as DragonFly. Any questions on the licensing issues should be directed to the DragonFly Team.
21 ## Port uhidd HID daemon from FreeBSD
25 *Shamelessly copied from the FreeBSD Wiki - https://wiki.freebsd.org/uhidd:
26 "uhidd is a userland driver/daemon for USB HID devices like mouse, keyboard etc. It is based on libusb20 and currently only works for FreeBSD 8.x and above".
28 *The uhidd driver would allow USB gaming controllers and joysticks to be used on DragonFlyBSD. uhidd also provide support for multimedia keys found on USB keyboards.
33 * This mainly involves porting uhidd and related items from FreeBSD.
38 * Being able to use USB game controllers and joysticks on DragonFly.
42 Bounty created at: 2020-02-17
70 ## Extend vkernel(7) to run on any POSIX OS
74 * vkernel(7) allows for running DragonFly kernels in userland. Still, it requires a DragonFly operating system.
76 * Similar to NetBSD's rumpkernel, allow the vkernel application to be independent of the operating system. Using a cross-compiler,
77 this would allow us to run a DragonFly kernel for instance on Linux or NetBSD (I know that running it within a virtual machine would be faster...).
82 * This mainly involves rewriting parts of the page-table handling code and interrupt-related code.
87 * Being able to run a vkernel binary on any POSIX OS.
91 Bounty created at: 2020-02-12
111 <td>TOTAL AMOUNT</td>
119 ## Hypervisor for DragonFly/x86_64
123 * Port nvmm (NetBSD) or bhyve (FreeBSD) to DragonFly.
125 ### Technical details
130 * Hardware-accelerated virtualization to run guest operating systems like Linux or Windows 10 on DragonFly.
131 * Support both Intel and AMD CPUs.
135 Bounty created at: 2020-02-12
169 <td>TOTAL AMOUNT</td>
170 <td>1150 USD + 500 CNY</td>
183 * Make Bluetooth work on DragonFly.
185 ### Technical details
187 We already have bluetooth support in the kernel which is based on netgraph6 (AFAIK).
188 It is disabled by default and is probably out of date.
190 We also have a partial and old netbt port from NetBSD...
193 * Research the current state of Bluetooth in DragonFly.
194 * Bluetooth is enabled by default when building the kernel/world.
195 * Bring in updates or re-port from FreeBSD/NetBSD.
196 * Bluetooth keyboard / mice is working.
197 * Bluetooth headphone is working.
201 Bounty created at: 2020-02-12
229 <td>TOTAL AMOUNT</td>
230 <td>250 USD + 300 CNY</td>
239 ## Full Rust libc FFI binding support
242 * Port Rust FFI libc bindings, in full to DragonFly.
244 ### Technical details
245 There has intermittently been some support on this and builds and tests have gone through periods of passing and failing, but a comprehensive buildout of full support of all features would make more advanced Rust development, especially as a viable web server backend more possible.
247 The Github URL is https://github.com/rust-lang/libc
250 * Ensure that all features available in our libc have been ported to working in the Rust FFI lib
251 * Ensure that the code builds
252 * Ensure that all tests pass
253 * Ensure at least a semi automated way for the upstream team to be able to continue validation by some sort of CI/CD system so that we don't have a large support divergence
281 <td>TOTAL AMOUNT</td>
293 * Port DragonFly to Aarch64
295 ### Technical details
317 <td>TOTAL AMOUNT</td>
324 ## UTF-8 support in Console
326 Adding full UTF-8 support in console.
328 ### Technical details
361 <td>TOTAL AMOUNT</td>
362 <td>35 EUR + 150 USD</td>
369 ## Port valgrind to DragonFlyBSD
371 (shamelessly copied from gsoc2010 projects page)
373 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.
375 ### Technical details
379 (shamelessly copied from gsoc2010 projects page)
381 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.
414 <td>TOTAL AMOUNT</td>
415 <td>150 EUR + 150 USD</td>
421 ## HAMMER compression
423 (shamelessly copied from gsoc2010 projects page)
425 * Compress blocks as they get written to disk.
426 * Only file data (rec_type == DATA) should be compressed, not meta-data.
427 * the CRC should be that of the uncompressed data.
428 * ideally you'd need to associate the uncompressed data with the buffer cache buffer somehow, so that decompression is only performed once.
429 * compression could be turned on a per-file or per-pfs basis.
430 * gzip compression would be just fine at first; lzo or lzjb might be preferable.
433 HAMMER2 has replaced HAMMER to be the default filesystem on DragonFly and is under active development and maintenance. HAMMER2 also has compression support.
435 ### Technical details
436 (shamelessly copied from gsoc2010 projects page)
438 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.
440 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).
471 <td>TOTAL AMOUNT</td>
472 <td>50 EUR + 150 USD</td>
478 ## Native NTFS support
480 (shamelessly copied from gsoc2010 projects page)
482 * Port Apple's native NTFS driver
484 ### Technical details
485 (shamelessly copied from gsoc2010 projects page)
487 Apple's NTFS native driver could be ported to DragonFly BSD. Latest code as of now is:
489 http://opensource.apple.com/source/ntfs/ntfs-84.40.1/kext/
510 <td>TOTAL AMOUNT</td>
520 As swildner wrote on 18th Septmber 2017: we need a new driver for a card reader.
522 RTS5209 PCI Express Card Reader
540 <td>TOTAL AMOUNT</td>
552 ##Port autofs from FreeBSD
554 Autofs allows dynamic filesystem mapping to render filesystems accessible, without keeping them mounted. It is designed as a modern, simpler, cleanroom reimplementation of amd.
571 <td>50 USD (paid)</td>
575 <td>TOTAL AMOUNT</td>
584 * Completely rip out our usb stack and replace it with FreeBSD's new usb4bsd (or whatever the FreeBSD-current USB stack is called nowadays).
585 * 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.
587 ### Technical details
606 <td>300 USD (paid)</td>
611 <td>100 USD (paid)</td>
616 <td>50 EUR (paid)</td>
621 <td>50 EUR (paid)</td>
625 <td>TOTAL AMOUNT</td>
626 <td>100 EUR + 400 USD</td>