From a0c4815433ccd57322f4f7703ca35e9ccfa59250 Mon Sep 17 00:00:00 2001 From: marha Date: Thu, 8 Oct 2009 13:15:52 +0000 Subject: Added MesaLib-7.6 --- mesalib/docs/helpwanted.html | 74 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 74 insertions(+) create mode 100644 mesalib/docs/helpwanted.html (limited to 'mesalib/docs/helpwanted.html') diff --git a/mesalib/docs/helpwanted.html b/mesalib/docs/helpwanted.html new file mode 100644 index 000000000..34afe49f7 --- /dev/null +++ b/mesalib/docs/helpwanted.html @@ -0,0 +1,74 @@ + + +Help Wanted + + + + + +

Help Wanted / To-Do List

+ +

+We can always use more help with the Mesa project. +Here are some specific ideas and areas where help would be appreciated: +

+ +
    +
  1. +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 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. +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 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. +

+ +

+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: +

+ +

    +
  1. Try to write high-quality code that follows the existing style. +
  2. Use uniform indentation, write comments, use meaningful identifiers, etc. +
  3. Test your code thoroughly. Include test programs if appropriate. +
+ + + + -- cgit v1.2.3