helpwanted.html revision b6c41fd9335eade8fdfc66d43a32fbf9994e4983 
1<HTML>
2
3<TITLE>Help Wanted</TITLE>
4
5<link rel="stylesheet" type="text/css" href="mesa.css"></head>
6
7<BODY>
8
9<H1>Help Wanted / To-Do List</H1>
10
11<p>
12We can always use more help with the Mesa project.
13Here are some specific ideas and areas where help would be appreciated:
14</p>
15
16<ol>
17<li>
18<b>Driver patching and testing.</b>
19Patches are often posted to the mesa3d-dev mailing list, but aren't
20immediately checked into git because not enough people are testing them.
21Just applying patches, testing and reporting back is helpful.
22<li>
23<b>Driver debugging.</b>
24There are plenty of open bugs in the bug database.
25<li>
26<b>Remove aliasing warnings.</b>
27Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing
28issues in the code.
29<li>
30<b>Windows driver building, testing and maintenance.</b>
31The Visual Studio project files aren't always updated in a timely manner
32when new source files are added or old ones are removed.
33Fixing these tends to delay new Mesa releases.
34<li>
35<b>Maintenance and testing of lesser-used drivers.</b>
36Drivers such as DOS/DJGPP, GGI, etc that aren't being maintained are being
37deprecated starting in Mesa 7.3.
38<li>
39<b>Contribute more tests to
40<a href="http://glean.sourceforge.net/" target="_parent">glean</a>.</b>
41<li>
42<b>Automatic testing.
43</b>
44It would be great if someone would set up an automated system for grabbing
45the latest Mesa code and run tests (such as glean) then report issues to
46the mailing list.
47</ol>
48
49
50<p>
51If you want to do something new in Mesa, first join the Mesa developer's
52mailing list.
53Then post a message to propose what you want to do, just to make sure
54there's no issues.
55</p>
56
57</p>
58Anyone is welcome to contribute code to the Mesa project.
59By doing so, it's assumed that you agree to the code's licensing terms.
60</p>
61
62<p>
63Finally:
64<p>
65
66<ol>
67<li>Try to write high-quality code that follows the existing style.
68<li>Use uniform indentation, write comments, use meaningful identifiers, etc.
69<li>Test your code thoroughly.  Include test programs if appropriate.
70</ol>
71
72
73</BODY>
74</HTML>
75