workbench/libs/mesa/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 / To-Do List</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>
  18 <b>Driver patching and testing.</b>
  19 Patches are often posted to the mesa3d-dev mailing list, but aren't
  20 immediately checked into git because not enough people are testing them.
  21 Just applying patches, testing and reporting back is helpful.
  22 <li>
  23 <b>Driver debugging.</b>
  24 There are plenty of open bugs in the bug database.
  25 <li>
  26 <b>Remove aliasing warnings.</b>
  27 Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing
  28 issues in the code.
  29 <li>
  30 <b>Windows driver building, testing and maintenance.</b>
  31 The Visual Studio project files aren't always updated in a timely manner
  32 when new source files are added or old ones are removed.
  33 Fixing these tends to delay new Mesa releases.
  34 <li>
  35 <b>Maintenance and testing of lesser-used drivers.</b>
  36 Drivers such as DOS/DJGPP, GGI, etc that aren't being maintained are being
  37 deprecated starting in Mesa 7.3.
  38 <li>
  39 <b>Contribute more tests to
  40 <a href="http://glean.sourceforge.net/" target="_parent">glean</a>.</b>
  41 <li>
  42 <b>Automatic testing.
  43 </b>
  44 It would be great if someone would set up an automated system for grabbing
  45 the latest Mesa code and run tests (such as glean) then report issues to
  46 the mailing list.
  47 </ol>
  48
  49
  50 <p>
  51 If you want to do something new in 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>