(no commit message)
[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.
d575682b 35***
62309341 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 43* Update our interrupt routing to ACPI interrupt routing instead of relying on the mptable exclusively
75837940 44* Update the PCI code to take advantage of MSI (Message Signalled Interrupts)
45 (PCI code *can* do MSI. It was synced w/FreeBSD 7.2 last year, just grep for MSI in bus/pci)
3ebcd5f1 46
62309341
R
47### Technical details
48Not yet written.
3ebcd5f1 49
62309341
R
50### Main goals
51Not yet written.
3ebcd5f1 52
53### Estimated time
62309341 54Unknown.
3ebcd5f1 55
62309341
R
56### Donators
57*** **Rumko** ***: 150 eur.
d575682b 58***
62309341 59 TOTAL AMOUNT 150 eur.
3ebcd5f1 60
62309341
R
61<br />
62## Port valgrind to DragonFlyBSD
63### Description
64(shamelessly copied from gsoc2010 projects page)
3ebcd5f1 65
62309341 66Valgrind 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 67
62309341
R
68### Technical details
69Not yet written.
3ebcd5f1 70
62309341
R
71### Main goals
72(shamelessly copied from gsoc2010 projects page)
3ebcd5f1 73
c0e7dd2a 74The 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 75
62309341
R
76### Estimated time
77Unknown.
3ebcd5f1 78
62309341
R
79### Donators
80*** **Rumko** ***: 100 eur.
11c9dd74 81
1f448e65 82*** **tuxillo** ***: 50 eur.
d575682b 83***
33291ce7 84 TOTAL AMOUNT 150 eur.
3ebcd5f1 85
62309341
R
86<br />
87## HAMMER compression
88### Description
89(shamelessly copied from gsoc2010 projects page)
90
91* Compress blocks as they get written to disk.
92* Only file data (rec_type == DATA) should be compressed, not meta-data.
93* the CRC should be that of the uncompressed data.
94* ideally you'd need to associate the uncompressed data with the buffer cache buffer somehow, so that decompression is only performed once.
95* compression could be turned on a per-file or per-pfs basis.
96* gzip compression would be just fine at first.
97
98### Technical details
99(shamelessly copied from gsoc2010 projects page)
3ebcd5f1 100
62309341 101Doing 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 102
62309341 103The 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 104
62309341
R
105### Main goals
106Not yet written.
107
108### Estimated time
109Unknown.
110
111### Donators
112*** **Rumko** ***: 50 eur.
d575682b 113***
62309341 114 TOTAL AMOUNT 50 eur.