1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <html lang="en"> 3 <head> 4 <meta http-equiv="content-type" content="text/html; charset=utf-8"> 5 <title>Help Wanted</title> 6 <link rel="stylesheet" type="text/css" href="mesa.css"> 7 </head> 8 <body> 9 10 <div class="header"> 11 <h1>The Mesa 3D Graphics Library</h1> 12 </div> 13 14 <iframe src="contents.html"></iframe> 15 <div class="content"> 16 17 <h1>Help Wanted / To-Do List</h1> 18 19 <p> 20 We can always use more help with the Mesa project. 21 Here are some specific ideas and areas where help would be appreciated: 22 </p> 23 24 <ol> 25 <li> 26 <b>Driver patching and testing.</b> 27 Patches are often posted to the <a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev">mesa-dev mailing list</a>, but aren't 28 immediately checked into git because not enough people are testing them. 29 Just applying patches, testing and reporting back is helpful. 30 <li> 31 <b>Driver debugging.</b> 32 There are plenty of open bugs in the <a href="https://bugs.freedesktop.org/describecomponents.cgi?product=Mesa">bug database</a>. 33 <li> 34 <b>Remove aliasing warnings.</b> 35 Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing 36 issues in the code. 37 <li> 38 <b>Contribute more tests to 39 <a href="https://piglit.freedesktop.org/">Piglit</a>.</b> 40 </ol> 41 42 <p> 43 You can find some further To-do lists here: 44 </p> 45 46 <p> 47 <b>Common To-Do lists:</b> 48 </p> 49 <ul> 50 <li><a href="https://cgit.freedesktop.org/mesa/mesa/tree/docs/features.txt"> 51 <b>features.txt</b></a> - Status of OpenGL 3.x / 4.x features in Mesa.</li> 52 </ul> 53 54 <p> 55 <b>Legacy Driver specific To-Do lists:</b> 56 </p> 57 <ul> 58 <li><a href="https://dri.freedesktop.org/wiki/R600ToDo"> 59 <b>r600g</b></a> - Driver for ATI/AMD R600 - Northern Island.</li> 60 <li><a href="https://dri.freedesktop.org/wiki/R300ToDo"> 61 <b>r300g</b></a> - Driver for ATI R300 - R500.</li> 62 </ul> 63 64 <p> 65 If you want to do something new in Mesa, first join the Mesa developer's 66 mailing list. 67 Then post a message to propose what you want to do, just to make sure 68 there's no issues. 69 </p> 70 71 <p> 72 Anyone is welcome to contribute code to the Mesa project. 73 By doing so, it's assumed that you agree to the code's licensing terms. 74 </p> 75 76 <p> 77 Finally: 78 </p> 79 80 <ol> 81 <li>Try to write high-quality code that follows the existing style. 82 <li>Use uniform indentation, write comments, use meaningful identifiers, etc. 83 <li>Test your code thoroughly. Include test programs if appropriate. 84 </ol> 85 86 </div> 87 </body> 88 </html> 89
