1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2<html lang="en">
3<head>
4  <meta http-equiv="content-type" content="text/html; charset=utf-8">
5  <title>Help Wanted</title>
6  <link rel="stylesheet" type="text/css" href="mesa.css">
7</head>
8<body>
9
10<div class="header">
11  <h1>The Mesa 3D Graphics Library</h1>
12</div>
13
14<iframe src="contents.html"></iframe>
15<div class="content">
16
17<h1>Help Wanted / To-Do List</h1>
18
19<p>
20We can always use more help with the Mesa project.
21Here are some specific ideas and areas where help would be appreciated:
22</p>
23
24<ol>
25<li>
26<b>Driver patching and testing.</b>
27Patches are often posted to the <a href="http://lists.freedesktop.org/mailman/listinfo/mesa-dev">mesa-dev mailing list</a>, but aren't
28immediately checked into git because not enough people are testing them.
29Just applying patches, testing and reporting back is helpful.
30<li>
31<b>Driver debugging.</b>
32There are plenty of open bugs in the <a href="https://bugs.freedesktop.org/describecomponents.cgi?product=Mesa">bug database</a>.
33<li>
34<b>Remove aliasing warnings.</b>
35Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing
36issues in the code.
37<li>
38<b>Windows driver building, testing and maintenance.</b>
39Fixing MSVC builds.
40<li>
41<b>Contribute more tests to
42<a href="http://piglit.freedesktop.org/">Piglit</a>.</b>
43<li>
44<b>Automatic testing.
45</b>
46It would be great if someone would set up an automated system for grabbing
47the latest Mesa code and run tests (such as piglit) then report issues to
48the mailing list.
49</ol>
50
51<p>
52You can find some further To-do lists here:
53</p>
54
55<p>
56<b>Common To-Do lists:</b>
57</p>
58<ul>
59  <li><a href="http://cgit.freedesktop.org/mesa/mesa/tree/docs/features.txt">
60    <b>features.txt</b></a> - Status of OpenGL 3.x / 4.x features in Mesa.</li>
61  <li><a href="http://dri.freedesktop.org/wiki/MissingFunctionality">
62    <b>MissingFunctionality</b></a> - Detailed information about missing OpenGL features.</li>
63</ul>
64
65<p>
66<b>Driver specific To-Do lists:</b>
67</p>
68<ul>
69  <li><a href="http://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/docs/llvm-todo.txt">
70    <b>LLVMpipe</b></a> - Software driver using LLVM for runtime code generation.</li>
71  <li><a href="http://dri.freedesktop.org/wiki/RadeonsiToDo">
72    <b>radeonsi</b></a> - Driver for AMD Southern Island.</li>
73  <li><a href="http://dri.freedesktop.org/wiki/R600ToDo">
74    <b>r600g</b></a> - Driver for ATI/AMD R600 - Northern Island.</li>
75  <li><a href="http://dri.freedesktop.org/wiki/R300ToDo">
76    <b>r300g</b></a> - Driver for ATI R300 - R500.</li>
77  <li><a href="http://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/drivers/i915/TODO">
78    <b>i915g</b></a> - Driver for Intel i915/i945.</li>
79</ul>
80
81<p>
82If you want to do something new in Mesa, first join the Mesa developer's
83mailing list.
84Then post a message to propose what you want to do, just to make sure
85there's no issues.
86</p>
87
88<p>
89Anyone is welcome to contribute code to the Mesa project.
90By doing so, it's assumed that you agree to the code's licensing terms.
91</p>
92
93<p>
94Finally:
95</p>
96
97<ol>
98<li>Try to write high-quality code that follows the existing style.
99<li>Use uniform indentation, write comments, use meaningful identifiers, etc.
100<li>Test your code thoroughly.  Include test programs if appropriate.
101</ol>
102
103</div>
104</body>
105</html>
106