docs/helpwanted.html

   1 <HTML>
   2
   3 <TITLE>Help Wanted</TITLE>
   4
   5 <link rel="stylesheet" type="text/css" href="mesa.css"></head>
   6
   7 <BODY>
   8
   9 <H1>Help Wanted</H1>
  10
  11 <p>
  12 We can always use more help with the Mesa project.
  13 Here are some specific ideas and areas where help would be appreciated:
  14 </p>
  15
  16 <ol>
  17 <li><p>
  18     Generate the src/mesa/main/enums.c file with a Python script which
  19     uses the gl_API.xml file.
  20     </p>
  21 <li><p>
  22     Try to auto-generate the display list "save" functions seen in dlist.c
  23     using a Python script and the gl_API.xml file.
  24     The gl_API.xml file will probably need a new tag to indicate whether or
  25     not each function gets compiled into display lists.
  26     </p>
  27 <li><p>
  28     Maintenance of assembly language files on Linux, Windows and SPARC systems.
  29     </p>
  30 <li><p>
  31     Help to incorporate the 3Dlabs' shading language compiler for OpenGL 2.0.
  32     </p>
  33 <li><p>
  34     Implement assembly language (SSE/MMX) code generation for
  35     vertex/fragment programs.
  36     </p>
  37 <li><p>
  38     Windows 98/NT driver building, maintenance and testing
  39     (Karl Schultz has been doing a great job of this lately).
  40     </p>
  41 <li><p>
  42     Maintenance and testing of various drivers, such as DOS/DJGPP, GGI, etc.
  43     </p>
  44 <li><p>
  45     Write new tests for Glean.
  46     </p>
  47 </ol>
  48
  49
  50 <p>
  51 If you want to help with Mesa, first join the Mesa developer's
  52 mailing list.
  53 Then post a message to propose what you want to do, just to make sure
  54 there's no issues.
  55 </p>
  56
  57 </p>
  58 Anyone is welcome to contribute code to the Mesa project.
  59 By doing so, it's assumed that you agree to the code's licensing terms.
  60 </p>
  61
  62 <p>
  63 Finally:
  64 <p>
  65
  66 <ol>
  67 <li>Try to write high-quality code that follows the existing style.
  68 <li>Use uniform indentation, write comments, use meaningful identifiers, etc.
  69 <li>Test your code thoroughly.  Include test programs if appropriate.
  70 </ol>
  71
  72
  73 </BODY>
  74 </HTML>