update NEWS for libva 2.4.0

[android-x86/hardware-intel-common-libva.git] / CONTRIBUTING.md

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 22de89b..0be5237 100644 (file)
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,6 +1,6 @@
 # Contributing to libva
 
-Libva is an open source project licensed under the [MIT License] (https://opensource.org/licenses/MIT)
+Libva is an open source project licensed under the [MIT License](https://opensource.org/licenses/MIT)
 
 ## Coding Style
 
@@ -8,7 +8,7 @@ Libva does not have a defined coding style at this time, but that will be update
 
 ## Certificate of Origin
 
-In order to get a clear contribution chain of trust we use the [signed-off-by language] (https://01.org/community/signed-process)
+In order to get a clear contribution chain of trust we use the [signed-off-by language](https://01.org/community/signed-process)
 used by the Linux kernel project.  
 ## Patch format
 
@@ -19,7 +19,7 @@ Beside the signed-off-by footer, we expect each patch to comply with the followi
 
 More detailed explanation of your changes: Why and how.
 Wrap it to 72 characters.
-See [here] (http://chris.beams.io/posts/git-commit/)
+See [here](http://chris.beams.io/posts/git-commit/)
 for some more good advices.
 
 Signed-off-by: <contributor@foo.com>
@@ -45,7 +45,11 @@ We accept github pull requests.
 
 Once you've finished making your changes push them to your fork and send the PR via the github UI.
 
-## Issue tracking
+## Reporting a security issue
+
+Please mail to secure-opensource@intel.com directly for security issue
+
+## Public issue tracking
 
 If you have a problem, please let us know.  IRC is a perfectly fine place
 to quickly informally bring something up, if you get a response.  The
@@ -53,14 +57,14 @@ to quickly informally bring something up, if you get a response.  The
 is a more durable communication channel.
 
 If it's a bug not already documented, by all means please [open an
-issue in github](https://github.com/01org/libva/issues/new) so we all get visibility
+issue in github](https://github.com/intel/libva/issues/new) so we all get visibility
 to the problem and can work towards a resolution.
 
 For feature requests we're also using github issues, with the label
 "enhancement".
 
 Our github bug/enhancement backlog and work queue are tracked in a
-[Libva waffle.io kanban](https://waffle.io/01org/libva).
+[Libva waffle.io kanban](https://waffle.io/intel/libva).
 
 ## Closing issues