Help Wanted
We can always use more help with the Mesa project. @@ -17,35 +24,43 @@ Here are some specific ideas and areas where help would be appreciated:
- Driver patching and testing. -Patches are often posted to the mesa-dev mailing list, but aren't +Patches are often posted to the mesa-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.
- Driver debugging. -There are plenty of open bugs in the bug database. +There are plenty of open bugs in the bug database.
- Remove aliasing warnings. -Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing -issues in the code. -
- -Windows driver building, testing and maintenance. -Fixing MSVC builds. -
-
-Maintenance and testing of lesser-used drivers.
-Drivers such as i810, mach64, mga, r128, savage, sis, tdfx, unichrome, etc that aren't being maintained are being
-deprecated starting in Mesa 8.0.
-They have to be ported to DRI2 to be accepted in mesa master again. +Enable gcc's-Wstrict-aliasing=2 -fstrict-aliasingarguments, and +track down aliasing issues in the code. - Contribute more tests to -Piglit. -
- -Automatic testing. - -It would be great if someone would set up an automated system for grabbing -the latest Mesa code and run tests (such as piglit) then report issues to -the mailing list. +Piglit.
+You can find some further To-do lists here: +
+ ++Common To-Do lists: +
+-
+
-
+
features.txt- Status of OpenGL 3.x / 4.x features in + Mesa.
+
+Legacy Driver specific To-Do lists: +
+If you want to do something new in Mesa, first join the Mesa developer's @@ -69,6 +84,6 @@ Finally: