From f901072afb4a48995e9e7c5a37d0c5704e55267c Mon Sep 17 00:00:00 2001 From: Brian Paul Date: Thu, 10 Feb 2005 15:18:26 +0000 Subject: lots of updates --- docs/helpwanted.html | 78 +++++++++++++++++++++++++++++----------------------- 1 file changed, 44 insertions(+), 34 deletions(-) (limited to 'docs/helpwanted.html') diff --git a/docs/helpwanted.html b/docs/helpwanted.html index 44b9067..346f093 100644 --- a/docs/helpwanted.html +++ b/docs/helpwanted.html @@ -9,54 +9,64 @@

Help Wanted

-We can always use more help with the Mesa project. Here are some -specific areas. If you think you can help out, post to the mesa3d-dev -mailing list. +We can always use more help with the Mesa project. +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. +

    +

If you want to help with Mesa, first join the Mesa developer's -mailing list. Then post a message explaining what you might like -to help with. The Mesa web page has a list of a few work items -which you may consider. +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, provided you -agree to the copyright terms of the relevant code. See the COPYRIGHT -file. +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.

-Unfortunately, all the easy work in Mesa was done years ago. Nowadays, the -work is rather complicated and not suited to beginners. -

- -

-If you're contribution code to the Mesa library itself: +Finally:

-

    -
  1. Try to write clean code (uniform indentation, comments, meaningful - identifiers, etc). It must be readable and maintainable! -
  2. Test your code. On several occations I've incorporated code from - users which later turned out to have bugs. Now, I'm pretty hesitant - to use code which doesn't look good. +
      +
    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.1