-<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>
-<link rel="stylesheet" type="text/css" href="mesa.css"></head>
+<iframe src="contents.html"></iframe>
+<div class="content">
-<BODY>
-
-<H1>Help Wanted / To-Do List</H1>
+<h1>Help Wanted</h1>
<p>
We can always use more help with the Mesa project.
<ol>
<li>
<b>Driver patching and testing.</b>
-Patches are often posted to the mesa3d-dev mailing list, but aren't
+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 bug database.
+There are plenty of open bugs in the <a href="https://gitlab.freedesktop.org/mesa/mesa/issues">bug database</a>.
<li>
<b>Remove aliasing warnings.</b>
-Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing
-issues in the code.
-<li>
-<b>Windows driver building, testing and maintenance.</b>
-The Visual Studio project files aren't always updated in a timely manner
-when new source files are added or old ones are removed.
-Fixing these tends to delay new Mesa releases.
-<li>
-<b>Maintenance and testing of lesser-used drivers.</b>
-Drivers such as DOS/DJGPP, GGI, etc that aren't being maintained are being
-deprecated starting in Mesa 7.3.
+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="http://glean.sourceforge.net/" target="_parent">glean</a>.</b>
-<li>
-<b>Automatic testing.
-</b>
-It would be great if someone would set up an automated system for grabbing
-the latest Mesa code and run tests (such as glean) then report issues to
-the mailing list.
+<a href="https://piglit.freedesktop.org/">Piglit</a>.</b>
</ol>
+<p>
+You can find some further To-do lists here:
+</p>
+
+<p>
+<b>Common To-Do lists:</b>
+</p>
+<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>
If you want to do something new in Mesa, first join the Mesa developer's
there's no issues.
</p>
-</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>
+</p>
<ol>
<li>Try to write high-quality code that follows the existing style.
<li>Test your code thoroughly. Include test programs if appropriate.
</ol>
-
-</BODY>
-</HTML>
+</div>
+</body>
+</html>
projects / mesa.git / blobdiff