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