From b16b9e4656e7199c2aec74a4c8ebc7a875d3ba73 Mon Sep 17 00:00:00 2001 From: Mike Gabriel Date: Mon, 2 Feb 2015 15:02:49 +0100 Subject: massive reduction of unneeded files --- nx-X11/extras/Mesa/docs/helpwanted.html | 74 --------------------------------- 1 file changed, 74 deletions(-) delete mode 100644 nx-X11/extras/Mesa/docs/helpwanted.html (limited to 'nx-X11/extras/Mesa/docs/helpwanted.html') diff --git a/nx-X11/extras/Mesa/docs/helpwanted.html b/nx-X11/extras/Mesa/docs/helpwanted.html deleted file mode 100644 index 346f093d6..000000000 --- a/nx-X11/extras/Mesa/docs/helpwanted.html +++ /dev/null @@ -1,74 +0,0 @@ - - -Help Wanted - - - - - -

Help Wanted

- -

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