Help Wanted — The Mesa 3D Graphics Library latest documentation

# Help Wanted

We can always use more help with the Mesa project. Here are some specific ideas and areas where help would be appreciated:

1. Driver testing. Most developers are working on newer hardware on the Mesa main branch, but older hardware often doesn’t have automated testing or as much testing coverage. Testing your older hardware for regressions and bisecting and fixing problems in those drivers is useful for other Linux users. You can also help by doing manual performance (or regression) testing work on performance changes being made in Mesa’s open merge requests.

2. Tasks up for grabs. There are ideas for improvements which other developers would like to see someone take on, but are explicitly up for grabs, under the difficulty: easy, difficulty: medium, and difficulty: hard labels.

3. Driver debugging. There are plenty of open bugs in the bug database.

4. Remove aliasing warnings. Enable GCC’s `-Wstrict-aliasing=2 -fstrict-aliasing` arguments, and track down aliasing issues in the code.

5. Contribute more tests to Piglit that aren’t covered by VK-GL-CTS.

You can find some further To-do lists here:

Common To-Do lists:

- features.txt - Status of OpenGL/OpenGLES and Vulkan features in Mesa across drivers.

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.

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.

Finally, be sure to review the instructions for submitting patches.