Ideally, we would like to rely on automation instead of adding extra burden to both new contributors and old-timers.
- read through the patch submission guide: https://wiki.winehq.org/Submitting_Patches
- put my real name on my Gitlab profile.
- not provide any disassemled or reverse engineered parts of Windows code. This includes ReactOS code.
This can be replaced by a CLA assistant bot, since these actions are expected to be taken once by the contributor.
- commit my patches with the same name locally, as provided on Gitlab. (See: https://wiki.winehq.org/Git_Wine_Tutorial)
- follow the basic style guidelines: https://wiki.winehq.org/Wine_Developer%27s_Guide/Coding_Practice#Some_notes_...
This can be replaced by CI automation with a lint stage.
- write regression tests for my patches, if needed.
This can probably be replaced by a bot that reminds the contributor to add tests if a patch that exceeds certain SLoC or cyclomatic complexity delta threshold is detected.