Clone of mesa.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

helpwanted.html 1.9KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364
  1. <HTML>
  2. <TITLE>Help Wanted</TITLE>
  3. <link rel="stylesheet" type="text/css" href="mesa.css"></head>
  4. <BODY>
  5. <H1>Help Wanted</H1>
  6. <p>
  7. We can always use more help with the Mesa project. Here are some
  8. specific areas. If you think you can help out, post to the mesa3d-dev
  9. mailing list.
  10. </p>
  11. <ul>
  12. <li>Windows 98/NT build/driver maintenance and testing (Karl Schultz has been
  13. doing a great job of this lately)
  14. <li>DOS/DJGPP build/driver maintenance and testing
  15. <li>GGI driver/build maintenance and testing
  16. <li>GNU autoconfig/libtool maintenance (esp. on non-Linux systems)
  17. <li>x86, SSE, 3DNow! and SPARC assembly language programming
  18. <li>Implement WGL font functions in the WGL interface code
  19. <li>Implement off-screen bitmap rendering support in the WGL interface code
  20. <li>Help with writing/testing the new NV_fragment_program extension code
  21. <li>Implement the ARB_vertex/fragment extensions
  22. <li>Download/compile/test Mesa and report any bugs found
  23. </ul>
  24. <p>
  25. If you want to help with Mesa, first join the Mesa developer's
  26. mailing list. Then post a message explaining what you might like
  27. to help with. The Mesa web page has a list of a few work items
  28. which you may consider.
  29. </p>
  30. </p>
  31. Anyone is welcome to contribute code to the Mesa project, provided you
  32. agree to the copyright terms of the relevant code. See the COPYRIGHT
  33. file.
  34. </p>
  35. <p>
  36. Unfortunately, all the easy work in Mesa was done years ago. Nowadays, the
  37. work is rather complicated and not suited to beginners.
  38. </p>
  39. <p>
  40. If you're contribution code to the Mesa library itself:
  41. <p>
  42. <ol>
  43. <li>Try to write clean code (uniform indentation, comments, meaningful
  44. identifiers, etc). It must be readable and maintainable!
  45. <li>Test your code. On several occations I've incorporated code from
  46. users which later turned out to have bugs. Now, I'm pretty hesitant
  47. to use code which doesn't look good.
  48. </ol>
  49. </BODY>
  50. </HTML>