diff options
Diffstat (limited to 'mesalib/docs/helpwanted.html')
| -rw-r--r-- | mesalib/docs/helpwanted.html | 30 |
1 files changed, 21 insertions, 9 deletions
diff --git a/mesalib/docs/helpwanted.html b/mesalib/docs/helpwanted.html index 444c12b5a..6d6058eb5 100644 --- a/mesalib/docs/helpwanted.html +++ b/mesalib/docs/helpwanted.html @@ -17,36 +17,48 @@ Here are some specific ideas and areas where help would be appreciated: <ol> <li> <b>Driver patching and testing.</b> -Patches are often posted to the mesa3d-dev mailing list, but aren't +Patches are often posted to the <a href="http://lists.freedesktop.org/mailman/listinfo/mesa-dev" target="_parent">mesa-dev mailing list</a>, but aren't immediately checked into git because not enough people are testing them. Just applying patches, testing and reporting back is helpful. <li> <b>Driver debugging.</b> -There are plenty of open bugs in the bug database. +There are plenty of open bugs in the <a href="https://bugs.freedesktop.org/describecomponents.cgi?product=Mesa" target="_parent">bug database</a>. <li> <b>Remove aliasing warnings.</b> Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing issues in the code. <li> <b>Windows driver building, testing and maintenance.</b> -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. <li> <b>Maintenance and testing of lesser-used drivers.</b> -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.<br> +They have to be ported to DRI2 to be accepted in mesa master again. <li> <b>Contribute more tests to -<a href="http://glean.sourceforge.net/" target="_parent">glean</a>.</b> +<a href="http://people.freedesktop.org/~nh/piglit/" target="_parent">Piglit</a>.</b> <li> <b>Automatic testing. </b> 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. </ol> +<p> +You can find some further To-do lists here: +</p> +<ul> + <li><a href="http://cgit.freedesktop.org/mesa/mesa/tree/docs/GL3.txt" + target="_parent"><b>GL3.txt</b></a></li> + <li><a href="http://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/docs/llvm-todo.txt" + target="_parent"><b>LLVMpipe - todo</b></a></li> + <li><a href="http://dri.freedesktop.org/wiki/MissingFunctionality" + target="_parent"><b>MissingFunctionality</b></a></li> + <li><a href="http://dri.freedesktop.org/wiki/R300ToDo" + target="_parent"><b>R300ToDo</b></a></li> +</ul> <p> If you want to do something new in Mesa, first join the Mesa developer's |