1848b8605Smrg<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2848b8605Smrg<html lang="en"> 3848b8605Smrg<head> 4848b8605Smrg <meta http-equiv="content-type" content="text/html; charset=utf-8"> 5848b8605Smrg <title>Help Wanted</title> 6848b8605Smrg <link rel="stylesheet" type="text/css" href="mesa.css"> 7848b8605Smrg</head> 8848b8605Smrg<body> 9848b8605Smrg 10848b8605Smrg<div class="header"> 11848b8605Smrg <h1>The Mesa 3D Graphics Library</h1> 12848b8605Smrg</div> 13848b8605Smrg 14848b8605Smrg<iframe src="contents.html"></iframe> 15848b8605Smrg<div class="content"> 16848b8605Smrg 17848b8605Smrg<h1>Help Wanted / To-Do List</h1> 18848b8605Smrg 19848b8605Smrg<p> 20848b8605SmrgWe can always use more help with the Mesa project. 21848b8605SmrgHere are some specific ideas and areas where help would be appreciated: 22848b8605Smrg</p> 23848b8605Smrg 24848b8605Smrg<ol> 25848b8605Smrg<li> 26848b8605Smrg<b>Driver patching and testing.</b> 27b8e80941SmrgPatches are often posted to the <a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev">mesa-dev mailing list</a>, but aren't 28848b8605Smrgimmediately checked into git because not enough people are testing them. 29848b8605SmrgJust applying patches, testing and reporting back is helpful. 30848b8605Smrg<li> 31848b8605Smrg<b>Driver debugging.</b> 32848b8605SmrgThere are plenty of open bugs in the <a href="https://bugs.freedesktop.org/describecomponents.cgi?product=Mesa">bug database</a>. 33848b8605Smrg<li> 34848b8605Smrg<b>Remove aliasing warnings.</b> 35848b8605SmrgEnable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing 36848b8605Smrgissues in the code. 37848b8605Smrg<li> 38848b8605Smrg<b>Contribute more tests to 39b8e80941Smrg<a href="https://piglit.freedesktop.org/">Piglit</a>.</b> 40848b8605Smrg</ol> 41848b8605Smrg 42848b8605Smrg<p> 43848b8605SmrgYou can find some further To-do lists here: 44848b8605Smrg</p> 45848b8605Smrg 46848b8605Smrg<p> 47848b8605Smrg<b>Common To-Do lists:</b> 48848b8605Smrg</p> 49848b8605Smrg<ul> 50b8e80941Smrg <li><a href="https://gitlab.freedesktop.org/mesa/mesa/blob/master/docs/features.txt"> 51b8e80941Smrg <b>features.txt</b></a> - Status of OpenGL 3.x / 4.x features in Mesa.</li> 52848b8605Smrg</ul> 53848b8605Smrg 54848b8605Smrg<p> 55b8e80941Smrg<b>Legacy Driver specific To-Do lists:</b> 56848b8605Smrg</p> 57848b8605Smrg<ul> 58b8e80941Smrg <li><a href="https://dri.freedesktop.org/wiki/R600ToDo"> 59848b8605Smrg <b>r600g</b></a> - Driver for ATI/AMD R600 - Northern Island.</li> 60b8e80941Smrg <li><a href="https://dri.freedesktop.org/wiki/R300ToDo"> 61848b8605Smrg <b>r300g</b></a> - Driver for ATI R300 - R500.</li> 62848b8605Smrg</ul> 63848b8605Smrg 64848b8605Smrg<p> 65848b8605SmrgIf you want to do something new in Mesa, first join the Mesa developer's 66848b8605Smrgmailing list. 67848b8605SmrgThen post a message to propose what you want to do, just to make sure 68848b8605Smrgthere's no issues. 69848b8605Smrg</p> 70848b8605Smrg 71848b8605Smrg<p> 72848b8605SmrgAnyone is welcome to contribute code to the Mesa project. 73848b8605SmrgBy doing so, it's assumed that you agree to the code's licensing terms. 74848b8605Smrg</p> 75848b8605Smrg 76848b8605Smrg<p> 77848b8605SmrgFinally: 78848b8605Smrg</p> 79848b8605Smrg 80848b8605Smrg<ol> 81848b8605Smrg<li>Try to write high-quality code that follows the existing style. 82848b8605Smrg<li>Use uniform indentation, write comments, use meaningful identifiers, etc. 83848b8605Smrg<li>Test your code thoroughly. Include test programs if appropriate. 84848b8605Smrg</ol> 85848b8605Smrg 86848b8605Smrg</div> 87848b8605Smrg</body> 88848b8605Smrg</html> 89