From 0b27aceae2464db3dd149cf4fd667e353a655c5e Mon Sep 17 00:00:00 2001 From: Brian Paul Date: Sat, 8 Mar 2003 17:38:57 +0000 Subject: Documentation/website overhaul. The website content and doc/ directory are now merged and are one and the same. --- docs/helpwanted.html | 62 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 docs/helpwanted.html (limited to 'docs/helpwanted.html') diff --git a/docs/helpwanted.html b/docs/helpwanted.html new file mode 100644 index 0000000000..b9434d0c03 --- /dev/null +++ b/docs/helpwanted.html @@ -0,0 +1,62 @@ + + +Help Wanted + + + +

Help Wanted

+ +

+We can always use more help with the Mesa project. Here are some +specific areas. If you think you can help out, post to the mesa3d-dev +mailing list. +

+ +

Windows 98/NT build/driver maintenance and testing (Karl Schultz has been + doing a great job of this lately) +
DOS/DJGPP build/driver maintenance and testing +
GGI driver/build maintenance and testing +
GNU autoconfig/libtool maintenance (esp. on non-Linux systems) +
x86, SSE, 3DNow! and SPARC assembly language programming +
Implement WGL font functions in the WGL interface code +
Implement off-screen bitmap rendering support in the WGL interface code +
Help with writing/testing the new NV_fragment_program extension code +
Implement the ARB_vertex/fragment extensions +
Download/compile/test Mesa and report any bugs found +

+ + +

+If you want to help with Mesa, first join the Mesa developer's +mailing list. Then post a message explaining what you might like +to help with. The Mesa web page has a list of a few work items +which you may consider. +

+ +

+Anyone is welcome to contribute code to the Mesa project, provided you +agree to the copyright terms of the relevant code. See the COPYRIGHT +file. +

+ +

+Unfortunately, all the easy work in Mesa was done years ago. Nowadays, the +work is rather complicated and not suited to beginners. +

+ +

+If you're contribution code to the Mesa library itself: +

Try to write clean code (uniform indentation, comments, meaningful + identifiers, etc). It must be readable and maintainable! + +
Test your code. On several occations I've incorporated code from + users which later turned out to have bugs. Now, I'm pretty hesitant + to use code which doesn't look good. +

+ + + + -- cgit v1.2.3