aboutsummaryrefslogtreecommitdiff
path: root/nx-X11/extras/Mesa_6.4.1/docs/helpwanted.html
blob: 346f093d64352ded15b97fa7de414ae269db02e3 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
<HTML>

<TITLE>Help Wanted</TITLE>

<link rel="stylesheet" type="text/css" href="mesa.css"></head>

<BODY>

<H1>Help Wanted</H1>

<p>
We can always use more help with the Mesa project.
Here are some specific ideas and areas where help would be appreciated:
</p>

<ol>
<li><p>
    Generate the src/mesa/main/enums.c file with a Python script which
    uses the gl_API.xml file.
    </p>
<li><p>
    Try to auto-generate the display list "save" functions seen in dlist.c
    using a Python script and the gl_API.xml file.
    The gl_API.xml file will probably need a new tag to indicate whether or
    not each function gets compiled into display lists.
    </p>
<li><p>
    Maintenance of assembly language files on Linux, Windows and SPARC systems.
    </p>
<li><p>
    Help to incorporate the 3Dlabs' shading language compiler for OpenGL 2.0.
    </p>
<li><p>
    Implement assembly language (SSE/MMX) code generation for
    vertex/fragment programs.
    </p>
<li><p>
    Windows 98/NT driver building, maintenance and testing
    (Karl Schultz has been doing a great job of this lately).
    </p>
<li><p>
    Maintenance and testing of various drivers, such as DOS/DJGPP, GGI, etc.
    </p>
<li><p>
    Write new tests for Glean.
    </p>
</ol>


<p>
If you want to help with Mesa, first join the Mesa developer's
mailing list.
Then post a message to propose what you want to do, just to make sure
there's no issues.
</p>

</p>
Anyone is welcome to contribute code to the Mesa project.
By doing so, it's assumed that you agree to the code's licensing terms.
</p>

<p>
Finally:
<p>

<ol>
<li>Try to write high-quality code that follows the existing style.
<li>Use uniform indentation, write comments, use meaningful identifiers, etc.
<li>Test your code thoroughly.  Include test programs if appropriate.
</ol>


</BODY>
</HTML>