From 24eebf4f88732e789a3d781d889541ed76c2e08e Mon Sep 17 00:00:00 2001 From: Andreas Boll Date: Mon, 25 Jun 2012 21:54:08 +0200 Subject: [PATCH] docs/helpwanted: update some info Signed-off-by: Brian Paul --- docs/helpwanted.html | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/docs/helpwanted.html b/docs/helpwanted.html index 444c12b5a9b..cfa057e4b70 100644 --- a/docs/helpwanted.html +++ b/docs/helpwanted.html @@ -17,33 +17,32 @@ 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. +Fixing MSVC builds.
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. +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.
Contribute more tests to -glean. +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 glean) then report issues to +the latest Mesa code and run tests (such as piglit) then report issues to the mailing list.

-- 2.30.2