Files
RedBear-OS/local/recipes/libs/mesa/source/docs/helpwanted.rst
T
vasilito cb424d7448 build: static patch-sanity linter (shift-left the malformed-patch class)
verify-patch-sanity.py validates every active recipe .patch has internally-
consistent hunk line counts — catching the 'malformed patch at line N' failure
at commit/CI/preflight time instead of hours into a cook. This cycle hit that
class three times (qtwaylandscanner, sddm, xwayland), each only discovered when
cookbook tried to apply the patch.

Running it across the repo found 29 latent malformed patches (validated against
GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22').
They were harmless only because they sit in vendored recipes (baked, not re-
applied) — but would fail on any version-bump re-derivation. --fix recounts the
hunk headers (body untouched) and repaired all 29.

Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test
(test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats
(empty placeholders, bare-@@ git hunks).
2026-08-01 05:13:02 +03:00

39 lines
1.6 KiB
ReStructuredText

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 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 <https://gitlab.freedesktop.org/mesa/mesa/-/issues>`__.
#. **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 <https://piglit.freedesktop.org/>`__ that aren't covered by
VK-GL-CTS.
You can find some further To-do lists here:
**Common To-Do lists:**
- `features.txt <https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/docs/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 :doc:`submitting
patches <submittingpatches>`.