blob: 444c12b5a9b144fb487c50ea0fde030187b63067 [file] [log] [blame]
Andreas Bollecd5c7c2012-06-12 09:05:03 +02001<!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>
Brian Paul0b27ace2003-03-08 17:38:57 +00009
Andreas Bollecd5c7c2012-06-12 09:05:03 +020010<h1>Help Wanted / To-Do List</h1>
Brian Paul0b27ace2003-03-08 17:38:57 +000011
12<p>
Brian Paulf9010722005-02-10 15:18:26 +000013We can always use more help with the Mesa project.
14Here are some specific ideas and areas where help would be appreciated:
Brian Paul0b27ace2003-03-08 17:38:57 +000015</p>
16
Brian Paulf9010722005-02-10 15:18:26 +000017<ol>
Brian7f80dc12007-10-31 09:44:01 -060018<li>
Brian Paulb6c41fd2009-01-22 09:58:52 -070019<b>Driver patching and testing.</b>
20Patches are often posted to the mesa3d-dev mailing list, 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 bug database.
26<li>
27<b>Remove aliasing warnings.</b>
28Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing
Brian7f80dc12007-10-31 09:44:01 -060029issues in the code.
30<li>
Brian Paulb6c41fd2009-01-22 09:58:52 -070031<b>Windows driver building, testing and maintenance.</b>
32The Visual Studio project files aren't always updated in a timely manner
33when new source files are added or old ones are removed.
34Fixing these tends to delay new Mesa releases.
Brian7f80dc12007-10-31 09:44:01 -060035<li>
Brian Paulb6c41fd2009-01-22 09:58:52 -070036<b>Maintenance and testing of lesser-used drivers.</b>
37Drivers such as DOS/DJGPP, GGI, etc that aren't being maintained are being
38deprecated starting in Mesa 7.3.
39<li>
40<b>Contribute more tests to
41<a href="http://glean.sourceforge.net/" target="_parent">glean</a>.</b>
42<li>
43<b>Automatic testing.
44</b>
45It would be great if someone would set up an automated system for grabbing
46the latest Mesa code and run tests (such as glean) then report issues to
47the mailing list.
Brian Paulf9010722005-02-10 15:18:26 +000048</ol>
Brian Paul0b27ace2003-03-08 17:38:57 +000049
50
51<p>
Brian Paulb6c41fd2009-01-22 09:58:52 -070052If you want to do something new in Mesa, first join the Mesa developer's
Brian Paulf9010722005-02-10 15:18:26 +000053mailing list.
54Then post a message to propose what you want to do, just to make sure
55there's no issues.
Brian Paul0b27ace2003-03-08 17:38:57 +000056</p>
57
Andreas Bolldf2be222012-06-12 09:05:22 +020058<p>
Brian Paulf9010722005-02-10 15:18:26 +000059Anyone is welcome to contribute code to the Mesa project.
60By doing so, it's assumed that you agree to the code's licensing terms.
Brian Paul0b27ace2003-03-08 17:38:57 +000061</p>
62
63<p>
Brian Paulf9010722005-02-10 15:18:26 +000064Finally:
Andreas Bolldf2be222012-06-12 09:05:22 +020065</p>
Brian Paul0b27ace2003-03-08 17:38:57 +000066
Brian Paul0b27ace2003-03-08 17:38:57 +000067<ol>
Brian Paulf9010722005-02-10 15:18:26 +000068<li>Try to write high-quality code that follows the existing style.
69<li>Use uniform indentation, write comments, use meaningful identifiers, etc.
70<li>Test your code thoroughly. Include test programs if appropriate.
Brian Paul0b27ace2003-03-08 17:38:57 +000071</ol>
72
73
Andreas Bollecd5c7c2012-06-12 09:05:03 +020074</body>
75</html>