Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / mesa3d / a437601bee5f79d66c61215ed381a240d1ea7287 / . / docs / helpwanted.html
blob: 34afe49f752afaf924f481019316cc5e5c64b8b4 [file] [log] [blame]
Brian Paul0b27ace2003-03-08 17:38:57 +0000[diff] [blame]1<HTML>
2
3<TITLE>Help Wanted</TITLE>
4
Brian Paul36da0452005-01-20 03:55:10 +0000[diff] [blame]5<link rel="stylesheet" type="text/css" href="mesa.css"></head>
6
7<BODY>
Brian Paul0b27ace2003-03-08 17:38:57 +0000[diff] [blame]8
Brian7f80dc12007-10-31 09:44:01 -0600[diff] [blame]9<H1>Help Wanted / To-Do List</H1>
Brian Paul0b27ace2003-03-08 17:38:57 +0000[diff] [blame]10
11<p>
Brian Paulf9010722005-02-10 15:18:26 +0000[diff] [blame]12We can always use more help with the Mesa project.
13Here are some specific ideas and areas where help would be appreciated:
Brian Paul0b27ace2003-03-08 17:38:57 +0000[diff] [blame]14</p>
15
Brian Paulf9010722005-02-10 15:18:26 +0000[diff] [blame]16<ol>
Brian7f80dc12007-10-31 09:44:01 -0600[diff] [blame]17<li>
Brian Paulb6c41fd2009-01-22 09:58:52 -0700[diff] [blame]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
Brian7f80dc12007-10-31 09:44:01 -0600[diff] [blame]28issues in the code.
29<li>
Brian Paulb6c41fd2009-01-22 09:58:52 -0700[diff] [blame]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.
Brian7f80dc12007-10-31 09:44:01 -0600[diff] [blame]34<li>
Brian Paulb6c41fd2009-01-22 09:58:52 -0700[diff] [blame]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.
Brian Paulf9010722005-02-10 15:18:26 +0000[diff] [blame]47</ol>
Brian Paul0b27ace2003-03-08 17:38:57 +0000[diff] [blame]48
49
50<p>
Brian Paulb6c41fd2009-01-22 09:58:52 -0700[diff] [blame]51If you want to do something new in Mesa, first join the Mesa developer's
Brian Paulf9010722005-02-10 15:18:26 +0000[diff] [blame]52mailing list.
53Then post a message to propose what you want to do, just to make sure
54there's no issues.
Brian Paul0b27ace2003-03-08 17:38:57 +0000[diff] [blame]55</p>
56
57</p>
Brian Paulf9010722005-02-10 15:18:26 +0000[diff] [blame]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.
Brian Paul0b27ace2003-03-08 17:38:57 +0000[diff] [blame]60</p>
61
62<p>
Brian Paulf9010722005-02-10 15:18:26 +0000[diff] [blame]63Finally:
64<p>
Brian Paul0b27ace2003-03-08 17:38:57 +0000[diff] [blame]65
Brian Paul0b27ace2003-03-08 17:38:57 +0000[diff] [blame]66<ol>
Brian Paulf9010722005-02-10 15:18:26 +0000[diff] [blame]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.
Brian Paul0b27ace2003-03-08 17:38:57 +0000[diff] [blame]70</ol>
71
72
73</BODY>
74</HTML>