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<h1>Help Wanted / To-Do List</h1>
11
12<p>
13We can always use more help with the Mesa project.
14Here are some specific ideas and areas where help would be appreciated:
15</p>
16
17<ol>
18<li>
19<b>Driver patching and testing.</b>
20Patches are often posted to the <a href="http://lists.freedesktop.org/mailman/listinfo/mesa-dev" target="_parent">mesa-dev mailing list</a>, but aren't
21immediately checked into git because not enough people are testing them.
22Just applying patches, testing and reporting back is helpful.
23<li>
24<b>Driver debugging.</b>
25There are plenty of open bugs in the <a href="https://bugs.freedesktop.org/describecomponents.cgi?product=Mesa" target="_parent">bug database</a>.
26<li>
27<b>Remove aliasing warnings.</b>
28Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing
29issues in the code.
30<li>
31<b>Windows driver building, testing and maintenance.</b>
32Fixing MSVC builds.
33<li>
34<b>Contribute more tests to
35<a href="http://piglit.freedesktop.org/" target="_parent">Piglit</a>.</b>
36<li>
37<b>Automatic testing.
38</b>
39It would be great if someone would set up an automated system for grabbing
40the latest Mesa code and run tests (such as piglit) then report issues to
41the mailing list.
42</ol>
43
44<p>
45You can find some further To-do lists here:
46</p>
47<ul>
48  <li><a href="http://cgit.freedesktop.org/mesa/mesa/tree/docs/GL3.txt"
49    target="_parent"><b>GL3.txt</b></a></li>
50  <li><a href="http://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/docs/llvm-todo.txt"
51    target="_parent"><b>LLVMpipe - todo</b></a></li>
52  <li><a href="http://dri.freedesktop.org/wiki/MissingFunctionality"
53    target="_parent"><b>MissingFunctionality</b></a></li>
54  <li><a href="http://dri.freedesktop.org/wiki/RadeonsiToDo"
55    target="_parent"><b>RadeonsiToDo</b></a></li>
56  <li><a href="http://dri.freedesktop.org/wiki/R600ToDo"
57    target="_parent"><b>R600ToDo</b></a></li>
58  <li><a href="http://dri.freedesktop.org/wiki/R300ToDo"
59    target="_parent"><b>R300ToDo</b></a></li>
60  <li><a href="http://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/drivers/i915/TODO"
61    target="_parent"><b>i915g TODO</b></a></li>
62</ul>
63
64<p>
65If you want to do something new in Mesa, first join the Mesa developer's
66mailing list.
67Then post a message to propose what you want to do, just to make sure
68there's no issues.
69</p>
70
71<p>
72Anyone is welcome to contribute code to the Mesa project.
73By doing so, it's assumed that you agree to the code's licensing terms.
74</p>
75
76<p>
77Finally:
78</p>
79
80<ol>
81<li>Try to write high-quality code that follows the existing style.
82<li>Use uniform indentation, write comments, use meaningful identifiers, etc.
83<li>Test your code thoroughly.  Include test programs if appropriate.
84</ol>
85
86
87</body>
88</html>
89