remove bogus entry
[ikiwiki.git] / docs / developer / Code_Bounties.mdwn
CommitLineData
3ebcd5f1 1[[!toc ]]
2
3ebcd5f1 3# Explanation
4
5A 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!).
6
3ebcd5f1 7# Rules
8
3ebcd5f1 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.
10
3ebcd5f1 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.
12
3ebcd5f1 13* 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.
14
3ebcd5f1 15* 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.
16
3ebcd5f1 17* All code submitted shall be of the same license as DragonFly. Any questions on the licensing issues should directed to the DragonFly Team.
18
3ebcd5f1 19# List of bounties
3ebcd5f1 20## UTF-8 support in Console
3ebcd5f1 21### Description
3ebcd5f1 22Adding full UTF-8 support in console.
23
3ebcd5f1 24### Technical details
62309341 25Not yet written.
3ebcd5f1 26
62309341 27### Main goals
3ebcd5f1 28Not yet written.
29
62309341
R
30### Estimated time
31Still unknown.
3ebcd5f1 32
62309341
R
33### Donators
34*** **timofonic** ***: 35 eur.
40f9f044 35
36*** **Dillon** ***: 50 usd.
d575682b 37***
40f9f044 38 TOTAL AMOUNT 35 eur + 50 usd.
3ebcd5f1 39
62309341
R
40<br />
41## Update our interrupt routing and PCI code
42### Description
43(shamelessly copied from gsoc2010 projects page)
3ebcd5f1 44
62309341 45* Update our interrupt routing to ACPI interrupt routing instead of relying on the mptable exclusively
75837940 46* Update the PCI code to take advantage of MSI (Message Signalled Interrupts)
47 (PCI code *can* do MSI. It was synced w/FreeBSD 7.2 last year, just grep for MSI in bus/pci)
3ebcd5f1 48
62309341
R
49### Technical details
50Not yet written.
3ebcd5f1 51
62309341
R
52### Main goals
53Not yet written.
3ebcd5f1 54
55### Estimated time
62309341 56Unknown.
3ebcd5f1 57
62309341
R
58### Donators
59*** **Rumko** ***: 150 eur.
40f9f044 60
61*** **Dillon** ***: 100 usd.
60a13d57 62
63*** **sjg** ***: 50 usd.
27c9f6d1 64
65*** **alexh** ***: 150 usd.
8a2d7c8f 66
67*** **JustinS** ***: 50 usd.
27c9f6d1 68***
8a2d7c8f 69 TOTAL AMOUNT 150 eur + 350 usd.
27c9f6d1 70
71<br />
72## Bring in usb4bsd
73### Description
74* Completely rip out our usb stack and replace it with FreeBSD's new usb4bsd (or whatever the FreeBSD-current USB stack is called nowadays).
87d94648 75* 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.
27c9f6d1 76
77### Technical details
78Not yet written.
79
80### Main goals
81Not yet written.
82
83### Estimated time
84Unknown.
85
86### Donators
87*** **alexh** ***: 100 usd.
6898fc24 88
6e38f23f 89*** **sjg** ***: 100 usd.
d575682b 90***
6e38f23f 91 TOTAL AMOUNT 200 usd.
3ebcd5f1 92
62309341
R
93<br />
94## Port valgrind to DragonFlyBSD
95### Description
96(shamelessly copied from gsoc2010 projects page)
3ebcd5f1 97
62309341 98Valgrind 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.
3ebcd5f1 99
62309341
R
100### Technical details
101Not yet written.
3ebcd5f1 102
62309341
R
103### Main goals
104(shamelessly copied from gsoc2010 projects page)
3ebcd5f1 105
c0e7dd2a 106The 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.
3ebcd5f1 107
62309341
R
108### Estimated time
109Unknown.
3ebcd5f1 110
62309341
R
111### Donators
112*** **Rumko** ***: 100 eur.
11c9dd74 113
1f448e65 114*** **tuxillo** ***: 50 eur.
40f9f044 115
116*** **Dillon** ***: 100 usd.
60a13d57 117
118*** **sjg** ***: 50 usd.
d575682b 119***
60a13d57 120 TOTAL AMOUNT 150 eur + 150 usd.
3ebcd5f1 121
62309341
R
122<br />
123## HAMMER compression
124### Description
125(shamelessly copied from gsoc2010 projects page)
126
127* Compress blocks as they get written to disk.
128* Only file data (rec_type == DATA) should be compressed, not meta-data.
129* the CRC should be that of the uncompressed data.
130* ideally you'd need to associate the uncompressed data with the buffer cache buffer somehow, so that decompression is only performed once.
131* compression could be turned on a per-file or per-pfs basis.
41124065 132* gzip compression would be just fine at first; lzo or lzjb might be preferable.
62309341
R
133
134### Technical details
135(shamelessly copied from gsoc2010 projects page)
3ebcd5f1 136
62309341 137Doing 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.
3ebcd5f1 138
62309341 139The 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).
3ebcd5f1 140
62309341
R
141### Main goals
142Not yet written.
143
144### Estimated time
145Unknown.
146
147### Donators
148*** **Rumko** ***: 50 eur.
40f9f044 149
150*** **Dillon** ***: 100 usd.
41124065 151
152*** **vsrinivas** ***: 50 usd.
153***
154 TOTAL AMOUNT 50 eur + 150 usd.
155