-<HTML>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html lang="en">
+<head>
+ <meta http-equiv="content-type" content="text/html; charset=utf-8">
+ <title>Help Wanted</title>
+ <link rel="stylesheet" type="text/css" href="mesa.css">
+</head>
+<body>
-<TITLE>Help Wanted</TITLE>
+<div class="header">
+ The Mesa 3D Graphics Library
+</div>
-<BODY text="#000000" bgcolor="#55bbff" link="#111188">
+<iframe src="contents.html"></iframe>
+<div class="content">
-<H1>Help Wanted</H1>
+<h1>Help Wanted</h1>
<p>
-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.
+We can always use more help with the Mesa project.
+Here are some specific ideas and areas where help would be appreciated:
</p>
-<ul>
-<li>Windows 98/NT build/driver maintenance and testing (Karl Schultz has been
- doing a great job of this lately)
-<li>DOS/DJGPP build/driver maintenance and testing
-<li>GGI driver/build maintenance and testing
-<li>GNU autoconfig/libtool maintenance (esp. on non-Linux systems)
-<li>x86, SSE, 3DNow! and SPARC assembly language programming
-<li>Implement WGL font functions in the WGL interface code
-<li>Implement off-screen bitmap rendering support in the WGL interface code
-<li>Help with writing/testing the new NV_fragment_program extension code
-<li>Implement the ARB_vertex/fragment extensions
-<li>Download/compile/test Mesa and report any bugs found
-</ul>
-
+<ol>
+<li>
+<b>Driver patching and testing.</b>
+Patches are often posted to the <a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev">mesa-dev mailing list</a>, but aren't
+immediately checked into git because not enough people are testing them.
+Just applying patches, testing and reporting back is helpful.
+<li>
+<b>Driver debugging.</b>
+There are plenty of open bugs in the <a href="https://bugs.freedesktop.org/describecomponents.cgi?product=Mesa">bug database</a>.
+<li>
+<b>Remove aliasing warnings.</b>
+Enable gcc's <code>-Wstrict-aliasing=2 -fstrict-aliasing</code> arguments, and
+track down aliasing issues in the code.
+<li>
+<b>Contribute more tests to
+<a href="https://piglit.freedesktop.org/">Piglit</a>.</b>
+</ol>
<p>
-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.
+You can find some further To-do lists here:
</p>
+<p>
+<b>Common To-Do lists:</b>
</p>
-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.
+<ul>
+ <li><a href="https://gitlab.freedesktop.org/mesa/mesa/blob/master/docs/features.txt">
+ <code>features.txt</code></a> - Status of OpenGL 3.x / 4.x features in
+ Mesa.</li>
+</ul>
+
+<p>
+<b>Legacy Driver specific To-Do lists:</b>
</p>
+<ul>
+ <li><a href="https://dri.freedesktop.org/wiki/R600ToDo">
+ <code>r600g</code></a> - Driver for ATI/AMD R600 - Northern Island.</li>
+ <li><a href="https://dri.freedesktop.org/wiki/R300ToDo">
+ <code>r300g</code></a> - Driver for ATI R300 - R500.</li>
+</ul>
<p>
-Unfortunately, all the easy work in Mesa was done years ago. Nowadays, the
-work is rather complicated and not suited to beginners.
+If you want to do something new in 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>
-If you're contribution code to the Mesa library itself:
+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>
-<ol>
-<li>Try to write clean code (uniform indentation, comments, meaningful
- identifiers, etc). It must be readable and maintainable!
+Finally:
+</p>
-<li>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.
+<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>
+</div>
+</body>
+</html>
projects / mesa.git / blobdiff