1Help Wanted
2===========
3
4We can always use more help with the Mesa project. Here are some
5specific ideas and areas where help would be appreciated:
6
7#. **Driver patching and testing.** Patches are often posted to the
8   `mesa-dev mailing
9   list <https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`__,
10   but aren't immediately checked into Git because not enough people are
11   testing them. Just applying patches, testing and reporting back is
12   helpful.
13#. **Driver debugging.** There are plenty of open bugs in the `bug
14   database <https://gitlab.freedesktop.org/mesa/mesa/-/issues>`__.
15#. **Remove aliasing warnings.** Enable GCC's
16   ``-Wstrict-aliasing=2 -fstrict-aliasing`` arguments, and track down
17   aliasing issues in the code.
18#. **Contribute more tests to**
19   `Piglit <https://piglit.freedesktop.org/>`__.
20
21You can find some further To-do lists here:
22
23**Common To-Do lists:**
24
25-  `features.txt <https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/docs/features.txt>`__
26   - Status of OpenGL 3.x / 4.x features in Mesa.
27
28**Legacy Driver specific To-Do lists:**
29
30-  `r600g <https://dri.freedesktop.org/wiki/R600ToDo>`__ - Driver
31   for ATI/AMD R600 - Northern Island.
32-  `r300g <https://dri.freedesktop.org/wiki/R300ToDo>`__ - Driver
33   for ATI R300 - R500.
34
35If you want to do something new in Mesa, first join the Mesa developer's
36mailing list. Then post a message to propose what you want to do, just
37to make sure there's no issues.
38
39Anyone is welcome to contribute code to the Mesa project. By doing so,
40it's assumed that you agree to the code's licensing terms.
41
42Finally:
43
44#. Try to write high-quality code that follows the existing style.
45#. Use uniform indentation, write comments, use meaningful identifiers,
46   etc.
47#. Test your code thoroughly. Include test programs if appropriate.
48