X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=docs%2Fhelpwanted.html;h=bee901314d23f32828622b21865cc94d3a6a2d54;hb=d6ec0aa7edfbe1c86861a4643b6b095a243d24ad;hp=346f093d64352ded15b97fa7de414ae269db02e3;hpb=f901072afb4a48995e9e7c5a37d0c5704e55267c;p=mesa.git diff --git a/docs/helpwanted.html b/docs/helpwanted.html index 346f093d643..bee901314d2 100644 --- a/docs/helpwanted.html +++ b/docs/helpwanted.html @@ -1,12 +1,20 @@ - + + + + + Help Wanted + + + -Help Wanted +
+

The Mesa 3D Graphics Library

+
- + +
- - -

Help Wanted

+

Help Wanted / To-Do List

We can always use more help with the Mesa project. @@ -14,54 +22,77 @@ Here are some specific ideas and areas where help would be appreciated:

    -
  1. - Generate the src/mesa/main/enums.c file with a Python script which - uses the gl_API.xml file. -

    -
  2. - Try to auto-generate the display list "save" functions seen in dlist.c - using a Python script and the gl_API.xml file. - The gl_API.xml file will probably need a new tag to indicate whether or - not each function gets compiled into display lists. -

    -
  3. - Maintenance of assembly language files on Linux, Windows and SPARC systems. -

    -
  4. - Help to incorporate the 3Dlabs' shading language compiler for OpenGL 2.0. -

    -
  5. - Implement assembly language (SSE/MMX) code generation for - vertex/fragment programs. -

    -
  6. - Windows 98/NT driver building, maintenance and testing - (Karl Schultz has been doing a great job of this lately). -

    -
  7. - Maintenance and testing of various drivers, such as DOS/DJGPP, GGI, etc. -

    -
  8. - Write new tests for Glean. -

    +
  9. +Driver patching and testing. +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. +
  10. +Driver debugging. +There are plenty of open bugs in the bug database. +
  11. +Remove aliasing warnings. +Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing +issues in the code. +
  12. +Windows driver building, testing and maintenance. +Fixing MSVC builds. +
  13. +Contribute more tests to +Piglit. +
  14. +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 piglit) then report issues to +the mailing list.
+

+You can find some further To-do lists here: +

+ +

+Common To-Do lists: +

+ + +

+Driver specific To-Do lists: +

+

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

-

+

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. @@ -69,6 +100,6 @@ Finally:
  2. Test your code thoroughly. Include test programs if appropriate.
- - - +
+ +