diff --git a/docs/helpwanted.rst b/docs/helpwanted.rst index 8ed54345538..ce513c7c70d 100644 --- a/docs/helpwanted.rst +++ b/docs/helpwanted.rst @@ -4,33 +4,28 @@ Help Wanted We can always use more help with the Mesa project. Here are some specific ideas and areas where help would be appreciated: -#. **Driver patching and testing.** Patches are often posted to the - `mesa-dev mailing - list `__, - but aren't immediately checked into Git because not enough people are - testing them. Just applying patches, testing and reporting back is - helpful. +#. **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. #. **Driver debugging.** There are plenty of open bugs in the `bug database `__. #. **Remove aliasing warnings.** Enable GCC's ``-Wstrict-aliasing=2 -fstrict-aliasing`` arguments, and track down aliasing issues in the code. #. **Contribute more tests to** - `Piglit `__. + `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 3.x / 4.x features in Mesa. - -**Legacy Driver specific To-Do lists:** - -- `r600g `__ - Driver - for ATI/AMD R600 - Northern Island. -- `r300g `__ - Driver - for ATI R300 - R500. + - 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 @@ -39,9 +34,5 @@ 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: - -#. Try to write high-quality code that follows the existing style. -#. Use uniform indentation, write comments, use meaningful identifiers, - etc. -#. Test your code thoroughly. Include test programs if appropriate. +Finally, be sure to review the instructions for :doc:`submitting +patches `.