summaryrefslogtreecommitdiff
path: root/docs/helpwanted.html
diff options
context:
space:
mode:
authorBrian Paul <brianp@vmware.com>2009-01-22 09:58:52 -0700
committerBrian Paul <brianp@vmware.com>2009-01-22 10:01:17 -0700
commitb6c41fd9335eade8fdfc66d43a32fbf9994e4983 (patch)
tree1098cd0f6e58a0100fcad5b45f0b903a6b0be3b9 /docs/helpwanted.html
parentb8bd0b0ddc357f9b430bb6ddeb60c5a2179d3791 (diff)
docs: assorted updates, link fixes
Diffstat (limited to 'docs/helpwanted.html')
-rw-r--r--docs/helpwanted.html31
1 files changed, 27 insertions, 4 deletions
diff --git a/docs/helpwanted.html b/docs/helpwanted.html
index 4cd92b97a9..34afe49f75 100644
--- a/docs/helpwanted.html
+++ b/docs/helpwanted.html
@@ -15,17 +15,40 @@ Here are some specific ideas and areas where help would be appreciated:
<ol>
<li>
-Enable -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing
+<b>Driver patching and testing.</b>
+Patches are often posted to the mesa3d-dev mailing list, but aren't
+immediately checked into git because not enough people are testing them.
+Just applying patches, testing and reporting back is helpful.
+<li>
+<b>Driver debugging.</b>
+There are plenty of open bugs in the bug database.
+<li>
+<b>Remove aliasing warnings.</b>
+Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing
issues in the code.
<li>
-Windows 98/NT driver building, maintenance and testing
+<b>Windows driver building, testing and maintenance.</b>
+The Visual Studio project files aren't always updated in a timely manner
+when new source files are added or old ones are removed.
+Fixing these tends to delay new Mesa releases.
+<li>
+<b>Maintenance and testing of lesser-used drivers.</b>
+Drivers such as DOS/DJGPP, GGI, etc that aren't being maintained are being
+deprecated starting in Mesa 7.3.
+<li>
+<b>Contribute more tests to
+<a href="http://glean.sourceforge.net/" target="_parent">glean</a>.</b>
<li>
-Maintenance and testing of lesser-used drivers, such as DOS/DJGPP, GGI, etc.
+<b>Automatic testing.
+</b>
+It would be great if someone would set up an automated system for grabbing
+the latest Mesa code and run tests (such as glean) then report issues to
+the mailing list.
</ol>
<p>
-If you want to help with Mesa, first join the Mesa developer's
+If you want to do something new in Mesa, first join the Mesa developer's
mailing list.
Then post a message to propose what you want to do, just to make sure
there's no issues.