Daniel Vetter | c15e693 | 2014-10-28 10:54:32 +0100 | [diff] [blame] | 1 | Patches to intel-gpu-tools are very much welcome, we really want this to be the |
| 2 | universal set of low-level tools and testcases for the Intel kernel gfx driver |
| 3 | on Linux and similar platforms. So please bring on porting patches, bugfixes, |
| 4 | improvements for documentation and new tools and testcases. |
| 5 | |
| 6 | A short list of contribution guidelines: |
| 7 | |
| 8 | - Please submit patches formatted with git send-email/git format-patch or |
| 9 | equivalent to |
| 10 | |
| 11 | Intel GFX discussion <intel-gfx@lists.freedesktop.org> |
| 12 | |
| 13 | Please use --subject-prefix="PATCH i-g-t" so that i-g-t patches are easily |
| 14 | identified in the massive amount mails on intel-gfx. To ensure this is always |
| 15 | done just run |
| 16 | |
| 17 | git config format.subjectprefix "PATCH i-g-t" |
| 18 | |
| 19 | from within your i-g-t git checkout. |
| 20 | |
| 21 | - intel-gpu-tools is MIT lincensed and we require contributions to follow the |
| 22 | developer's certificate of origin: http://developercertificate.org/ |
| 23 | |
| 24 | - When submitting new testcases please follow the naming conventions documented |
Daniel Vetter | 25c4347 | 2015-02-07 12:45:49 +0100 | [diff] [blame] | 25 | in the generated documentation. Also please make full use of all the helpers and |
Daniel Vetter | c15e693 | 2014-10-28 10:54:32 +0100 | [diff] [blame] | 26 | convenience macros provided by the igt library. The semantic patch lib/igt.cocci |
| 27 | can help with the more automatic conversions. |
| 28 | |
| 29 | - There is no formal review requirement and regular contributors with commit |
| 30 | access can push patches right after submitting them to the mailing lists. But |
| 31 | invasive changes, new helper libraries and contributions from newcomers should |
| 32 | go through a proper review to ensure overall consistency in the codebase. |
| 33 | |
| 34 | - When patches from new contributors (without commit access) are stuck, for |
| 35 | anything related to the regular releases, issues with packaging and |
Thomas Wood | e80922e | 2014-12-05 14:07:53 +0000 | [diff] [blame] | 36 | integrating platform support or any other intel-gpu-tools issues, please |
| 37 | contact one of the maintainers (listed in the MAINTAINERS file) and cc the |
| 38 | intel-gfx mailing list. |
Daniel Vetter | c15e693 | 2014-10-28 10:54:32 +0100 | [diff] [blame] | 39 | |
| 40 | - Especially changes to the testcase should get tested on relevant platforms |
| 41 | before committing. For Intel employees that's best done using PRTS, see the |
| 42 | relevant internal howtos. Everyone else can just run piglit with i-g-t tests |
| 43 | locally. |
| 44 | |
| 45 | Happy hacking! |