Code Bounties
- Code Bounties
- Explanation
- Rules
- Active bounties
- In-kernel WireGuard port
- Bring in support for USB webcams
- Port uhidd HID daemon from FreeBSD
- Extend vkernel(7) to run on any POSIX OS
- Bluetooth-Support
- Full Rust libc FFI binding support
- More Modern Thunderbolt Support
- OpenPower9 Support
- AArch64 support
- UTF-8 support in Console
- HAMMER compression
- Native NTFS support
- Card reader driver
- Completed 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 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.
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.
All code submitted shall be of the same license as DragonFly. Any questions on the licensing issues should be directed to the DragonFly Team.
Active bounties
In-kernel WireGuard port
Description
WireGuard is an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. It aims to be faster, simpler, leaner, and more useful than IPsec, while avoiding the massive headache. It intends to be considerably more performant than OpenVPN. WireGuard is designed as a general purpose VPN for running on embedded interfaces and super computers alike, fit for many different circumstances. Initially released for the Linux kernel, it is now cross-platform (Windows, macOS, BSD, iOS, Android) and widely deployable. (copied from WireGuard official website)
We already have the userland implementation in Golang in DPorts (i.e., wireguard-go).
It would be better to also gain the in-kernel implementation, like OpenBSD and FreeBSD already did.
Technical details
- Port WireGuard directly from the upstream or from OpenBSD/FreeBSD.
- The crypto framework might need an update (from OpenBSD/FreeBSD).
NOTE: The initial port by FreeBSD/Netgate was buggy, so need to investigate before using that code. See: Buffer overruns, license violations, and bad code: FreeBSD 13's close call
The re-port of WireGuard to FreeBSD: [ANNOUNCE] WireGuard for FreeBSD in development for 13.y – and a note of how we got here.
The Author (Jason A. Donenfeld) also said "the crypto needed to be re-accelerated", as detailed in if_wg simd chapoly needs some love.
NOTE: NetBSD has a separate from-sratch implementation wg(4). The code looks quite clean and nice. So it maybe a good idea to port the NetBSD version.
See also the dispute between WireGuard's author and NetBSD developers: "wireguard" implementation improperly merged and needs revert
Main goals
- WireGuard port in DragonFly kernel, as well as the userland tools.
- WireGuard works.
- The port should be ideally reviewed/audited by the WireGuard project. I (aly@) believe the author (Jason A. Donenfeld) would like to help.
Actuality
Created at: 2021-08-12
Estimated time
Unknown.
Donators
| Donor | Amount |
|---|---|
| aly (Aaron LI) | 100 USD |
| bycn82 (Bill Yuan) | 100 USD |
| TOTAL AMOUNT | 200 USD |
Bring in support for USB webcams
Description
Bring in uvideo from NetBSD or OpenBSD, and the dependent video driver. If you think that webcam support in FreeBSD is superior, feels free to bring in cuse etc.
Final result should be that USB webcams are usable from chrome or firefox for the purpose of video conferencing (e.g. via jitsi.org). Personally I only need support for low-quality webcams, no need for 4k :).
Actuality
Bounty created at: 2021-08-08
Estimated time
Unknown.
Donators
| Donor | Amount |
|---|---|
| mneumann | 150 USD |
| pikrzyszt | 100 GBP |
| aly | 50 USD |
| TOTAL AMOUNT | 200 USD + 100 GBP |
Port uhidd HID daemon from FreeBSD
Description
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.
The uhidd driver would allow USB gaming controllers and joysticks to be used on DragonFly BSD. uhidd also provide support for multimedia keys found on USB keyboards.
(Derived from the FreeBSD Wiki: uhidd)
Technical details
- This mainly involves porting uhidd and related items from FreeBSD.
Main goals
- Being able to use USB game controllers and joysticks on DragonFly.
Actuality
Bounty created at: 2020-02-17
Estimated time
Unknown.
Donators
| Donor | Amount |
|---|---|
| kerma | 100 USD |
| TOTAL AMOUNT | 100 USD |
Extend vkernel(7) to run on any POSIX OS
Description
vkernel(7) allows for running DragonFly kernels in userland. Still, it requires a DragonFly operating system.
Similar to NetBSD's rumpkernel, allow the vkernel application to be independent of the operating system. Using a cross-compiler, 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...).
Technical details
- This mainly involves rewriting parts of the page-table handling code and interrupt-related code.
Main goals
- Being able to run a vkernel binary on any POSIX OS.
Actuality
Bounty created at: 2020-02-12
Estimated time
Unknown.
Donators
| Donor | Amount |
|---|---|
| mneumann | 100 USD |
| TOTAL AMOUNT | 100 USD |
Bluetooth-Support
Description
- Make Bluetooth work on DragonFly.
Technical details
We already have bluetooth support in the kernel which is based on netgraph6 (AFAIK). It is disabled by default and is probably out of date.
We also have a partial and old netbt port from NetBSD...
Main goals
- Research the current state of Bluetooth in DragonFly.
- Bluetooth is enabled by default when building the kernel/world.
- Bring in updates or re-port from FreeBSD/NetBSD.
- Bluetooth keyboard / mice is working.
- Bluetooth headphone is working.
Actuality
Bounty created at: 2020-02-12
Estimated time
Unknown.
Donators
| Donor | Amount |
|---|---|
| mneumann | 200 USD |
| tuxillo | 50 USD |
| aly | 50 USD |
| TOTAL AMOUNT | 300 USD |
Full Rust libc FFI binding support
Description
- Port Rust FFI libc bindings, in full to DragonFly.
Technical details
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.
The Github URL is https://github.com/rust-lang/libc
Main goals
- Ensure that all features available in our libc have been ported to working in the Rust FFI lib
- Ensure that the code builds
- Ensure that all tests pass
- 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
Estimated time
Unknown.
Donators
| Donor | Amount |
|---|---|
| zach | 400 USD |
| joris | 150 USD |
| profmakx | 200 USD |
| TOTAL AMOUNT | 750 USD |
More Modern Thunderbolt Support
Description
- Integrate Thunderbolt Devices
Technical Details
To be defined
Main Goals
Not Yet Written
Estimated Time
Unknown
Donators
| Donor | Amount |
|---|---|
| Mike Carroll | 150 USD |
| TOTAL AMOUNT | 150 USD |
OpenPower9 Support
Description
- Port DragonFly to OpenPower 9 CPUs
Technical Details
To be defined
Main Goals
Not Yet Written
Estimated Time
Unknown
Donators
| Donor | Amount |
|---|---|
| Mike Carroll | 150 USD |
| TOTAL AMOUNT | 150 USD |
AArch64 support
Description
- Port DragonFly to Aarch64
Technical details
To be defined
Main goals
Not yet written.
Estimated time
Unknown.
Donators
| Donor | Amount |
|---|---|
| tuxillo | 100 EUR |
| Mike Carroll | 150 USD |
| TOTAL AMOUNT | 100 EUR + 150 USD |
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
| Donor | Amount |
|---|---|
| timofonic | 35 EUR |
| dillon | 50 USD |
| kerma | 100 USD |
| TOTAL AMOUNT | 35 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.
NOTE: HAMMER2 has replaced HAMMER to be the default filesystem on DragonFly and is under active development and maintenance. HAMMER2 also has compression support.
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
| Donor | Amount |
|---|---|
| rumko | 50 EUR |
| dillon | 100 USD |
| vsrinivas | 50 USD |
| TOTAL AMOUNT | 50 EUR + 150 USD |
Native NTFS support
Description
(shamelessly copied from gsoc2010 projects page)
- Port Apple's native NTFS driver
Technical details
(shamelessly copied from gsoc2010 projects page)
Apple's NTFS native driver could be ported to DragonFly BSD.
Latest code as of now is: http://opensource.apple.com/source/ntfs/ntfs-84.40.1/kext/
Main goals
Not yet written.
Estimated time
Unknown.
Donators
| Donor | Amount |
|---|---|
| tuxillo | 75 EUR |
| TOTAL AMOUNT | 75 EUR |
Card reader driver
Description
As swildner wrote on 18th Septmber 2017: we need a new driver for a card reader.
RTS5209 PCI Express Card Reader
Estimated time
Unknown.
Donators
| Donor | Amount |
|---|---|
| ferz | 20 EUR |
| TOTAL AMOUNT | 20 EUR |
Completed Bounties
Port valgrind to DragonFlyBSD [TAKEN 2021-03-30]
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.
Bounty status
Taken by dan_.
Repository: Github
Donators
| Donor | Amount |
|---|---|
| rumko | 100 EUR |
| tuxillo | 50 EUR |
| dillon | 100 USD |
| sjg | 50 USD |
| TOTAL AMOUNT | 150 EUR + 150 USD (paid) |
Hypervisor for DragonFly/x86_64
Description
- Port nvmm (NetBSD) or bhyve (FreeBSD) to DragonFly.
Technical details
Employ Intel VT-x and AMD SVM to provide fast virtualization support for running various guest OSes.
Main goals
- Hardware-accelerated virtualization to run guest operating systems like Linux or Windows 10 on DragonFly.
- Support both Intel and AMD CPUs.
Actuality
Created at: 2020-02-12
Completed at: 2021-08-08
Estimated time
Unknown.
Bounty status
Completed by: Aaron LI (aly@)
Previous Party: Kamil Rytarowski (kamil at netbsd dot org)
Previous Repository: https://github.com/Moritz-Systems/DragonFlyBSD
Results
- Ported NVMM from NetBSD-current (as of 2021-06-25), plus various improvements/fixes from maxv's repo.
- Support both Intel VMX and AMD SVM on x86_64 CPUs.
- Components:
- nvmm(4): kernel module, including both the MI frontend and MD backends
- libnvmm(3): hypervisor API interacting with nvmm(4), e.g., used by QEMU
- nvmmctl(8): utility to inspect NVMM status (still premilinary)
- testcases/libnvmm: libnvmm test cases
- test/nvmm: examples
- Merged into master (6.1) on 2021-07-20.
- QEMU (6.0.0) has been updated to employ NVMM on DragonFly and available in DPorts: emulators/qemu60.
- HowTo document: Virtualization: NVMM Hypervisor
Donators
| Donor | Amount |
|---|---|
| mneumann | 500 USD (paid) |
| tuxillo | 175 USD (paid) |
| kerma | 500 USD (paid) |
| aly | 500 CNY (myself ;)) |
| TOTAL AMOUNT | 1175 USD + 500 CNY |
Port autofs from FreeBSD
Description
Autofs allows dynamic filesystem mapping to render filesystems accessible, without keeping them mounted. It is designed as a modern, simpler, cleanroom reimplementation of amd.
Main goals
Not yet written.
Estimated time
Unknown.
Donators
| Donor | Amount |
|---|---|
| kerma | 50 USD (paid) |
| TOTAL AMOUNT | 50 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
| Donor | Amount |
|---|---|
| alexh | 300 USD (paid) |
| sjg | 100 USD (paid) |
| ferz | 50 EUR (paid) |
| tuxillo | 50 EUR (paid) |
| TOTAL AMOUNT | 100 EUR + 400 USD |