1 # Contributing to libva
3 Libva is an open source project licensed under the [MIT License] (https://opensource.org/licenses/MIT)
7 Libva does not have a defined coding style at this time, but that will be updated.
9 ## Certificate of Origin
11 In order to get a clear contribution chain of trust we use the [signed-off-by language] (https://01.org/community/signed-process)
12 used by the Linux kernel project.
16 Beside the signed-off-by footer, we expect each patch to comply with the following format:
19 <component>: Change summary
21 More detailed explanation of your changes: Why and how.
22 Wrap it to 72 characters.
23 See [here] (http://chris.beams.io/posts/git-commit/)
24 for some more good advices.
26 Signed-off-by: <contributor@foo.com>
32 drm: remove va_drm_is_authenticated check
34 If we do not use a render node we must authenticate. Doing the extra
35 GetClient calls/ioctls does not help much, so don't bother.
37 Cc: David Herrmann <dh.herrmann@gmail.com>
38 Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
39 Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
40 Reviewed-by: Sean V Kelley <seanvk@posteo.de>
45 We accept github pull requests.
47 Once you've finished making your changes push them to your fork and send the PR via the github UI.
51 If you have a problem, please let us know. IRC is a perfectly fine place
52 to quickly informally bring something up, if you get a response. The
53 [mailing list](http://lists.freedesktop.org/mailman/listinfo/libva)
54 is a more durable communication channel.
56 If it's a bug not already documented, by all means please [open an
57 issue in github](https://github.com/01org/libva/issues/new) so we all get visibility
58 to the problem and can work towards a resolution.
60 For feature requests we're also using github issues, with the label
63 Our github bug/enhancement backlog and work queue are tracked in a
64 [Libva waffle.io kanban](https://waffle.io/01org/libva).
68 You can either close issues manually by adding the fixing commit SHA1 to the issue
69 comments or by adding the `Fixes` keyword to your commit message:
72 ssntp: test: Add Disconnection role checking tests
74 We check that we get the right role from the disconnection
79 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
82 Github will then automatically close that issue when parsing the
83 [commit message](https://help.github.com/articles/closing-issues-via-commit-messages/).