From b6c41fd9335eade8fdfc66d43a32fbf9994e4983 Mon Sep 17 00:00:00 2001 From: Brian Paul Date: Thu, 22 Jan 2009 09:58:52 -0700 Subject: docs: assorted updates, link fixes --- docs/helpwanted.html | 31 +++++++++++++++++++++++++++---- 1 file changed, 27 insertions(+), 4 deletions(-) (limited to 'docs/helpwanted.html') 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:
  1. -Enable -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing +Driver patching and testing. +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. +
  2. +Driver debugging. +There are plenty of open bugs in the bug database. +
  3. +Remove aliasing warnings. +Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing issues in the code.
  4. -Windows 98/NT driver building, maintenance and testing +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. +
  5. +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. +
  6. +Contribute more tests to +glean.
  7. -Maintenance and testing of lesser-used drivers, such as DOS/DJGPP, GGI, etc. +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.

-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. -- cgit v1.2.3