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