3 new bounties ... valgrind, interrupt routing and hammer compression
[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.
35----------
36 TOTAL AMOUNT 35 eur.
3ebcd5f1 37
62309341
R
38<br />
39## Update our interrupt routing and PCI code
40### Description
41(shamelessly copied from gsoc2010 projects page)
3ebcd5f1 42
62309341
R
43* Update our interrupt routing to ACPI interrupt routing instead of relying on the mptable exclusively
44* Update the PCI code to take advantage of MSI (Message Signalled Interrupts)
3ebcd5f1 45
62309341
R
46### Technical details
47Not yet written.
3ebcd5f1 48
62309341
R
49### Main goals
50Not yet written.
3ebcd5f1 51
52### Estimated time
62309341 53Unknown.
3ebcd5f1 54
62309341
R
55### Donators
56*** **Rumko** ***: 150 eur.
57----------
58 TOTAL AMOUNT 150 eur.
3ebcd5f1 59
62309341
R
60<br />
61## Port valgrind to DragonFlyBSD
62### Description
63(shamelessly copied from gsoc2010 projects page)
3ebcd5f1 64
62309341 65Valgrind 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 66
62309341
R
67### Technical details
68Not yet written.
3ebcd5f1 69
62309341
R
70### Main goals
71(shamelessly copied from gsoc2010 projects page)
3ebcd5f1 72
62309341 73The goal of this project is to port valgrind to the DragonFlyBSD platform so that at least the memcheck tool runs sufficiently well to be useful.
3ebcd5f1 74
62309341
R
75### Estimated time
76Unknown.
3ebcd5f1 77
62309341
R
78### Donators
79*** **Rumko** ***: 100 eur.
3ebcd5f1 80----------
62309341 81 TOTAL AMOUNT 100 eur.
3ebcd5f1 82
62309341
R
83<br />
84## HAMMER compression
85### Description
86(shamelessly copied from gsoc2010 projects page)
87
88* Compress blocks as they get written to disk.
89* Only file data (rec_type == DATA) should be compressed, not meta-data.
90* the CRC should be that of the uncompressed data.
91* ideally you'd need to associate the uncompressed data with the buffer cache buffer somehow, so that decompression is only performed once.
92* compression could be turned on a per-file or per-pfs basis.
93* gzip compression would be just fine at first.
94
95### Technical details
96(shamelessly copied from gsoc2010 projects page)
3ebcd5f1 97
62309341 98Doing 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 99
62309341 100The 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 101
62309341
R
102### Main goals
103Not yet written.
104
105### Estimated time
106Unknown.
107
108### Donators
109*** **Rumko** ***: 50 eur.
110----------
111 TOTAL AMOUNT 50 eur.