Help Wanted
We can always use more help with the Mesa project. @@ -17,36 +24,43 @@ Here are some specific ideas and areas where help would be appreciated:
- Driver patching and testing. -Patches are often posted to the mesa3d-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. -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. -
-
-Maintenance and testing of lesser-used drivers.
-Drivers such as DOS/DJGPP, GGI, etc that aren't being maintained are being
-deprecated starting in Mesa 7.3.
+Enable gcc's
-Wstrict-aliasing=2 -fstrict-aliasingarguments, and +track down aliasing issues in the code. - Contribute more tests to -glean. -
- -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 glean) 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 @@ -55,14 +69,14 @@ Then post a message to propose what you want to do, just to make sure there's no issues.
- +Anyone is welcome to contribute code to the Mesa project. By doing so, it's assumed that you agree to the code's licensing terms.
Finally: -
+
- Try to write high-quality code that follows the existing style. @@ -70,6 +84,6 @@ Finally:
- Test your code thoroughly. Include test programs if appropriate.