summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHaihao Xiang <haihao.xiang@intel.com>2018-03-14 12:45:32 +0800
committerXiang, Haihao <haihao.xiang@intel.com>2018-03-15 09:37:16 +0800
commit6286f8f80f8fb6aed56278ad82e22bfb5e5615d1 (patch)
tree4b917cfda362c29ea4d852c2e5c9d9588b074d08
parent7c5820d07db4c686be0866e17d27c1e798f784f0 (diff)
downloadlibva-intel-driver-6286f8f80f8fb6aed56278ad82e22bfb5e5615d1.tar.gz
Use the new link URLs
We moved libva from github/01org to github/intel, however some files still have links to the old 01org URLs, this commit updates these links to the new intel URLs. In addition, this commit added a contact email address for security issue reporting This fixes https://github.com/intel/intel-vaapi-driver/issues/364 Signed-off-by: Haihao Xiang <haihao.xiang@intel.com>
-rw-r--r--.travis.yml4
-rw-r--r--CONTRIBUTING.md10
-rw-r--r--README.md10
-rw-r--r--configure.ac4
4 files changed, 16 insertions, 12 deletions
diff --git a/.travis.yml b/.travis.yml
index b0d5f499..807234bb 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -42,13 +42,13 @@ before_install:
- sudo apt-get install -y intel-gpu-tools
install:
- - git clone https://github.com/01org/libva.git
+ - git clone https://github.com/intel/libva.git
- (cd libva && ./autogen.sh && ./configure --prefix=/usr && sudo make install)
addons:
coverity_scan:
project:
- name: "01org/intel-vaapi-driver"
+ name: "intel/intel-vaapi-driver"
description: "Build submitted via Travis CI"
notification_email: intel-media-security@lists.01.org
build_command_prepend: "./autogen.sh; ./configure --prefix=/usr"
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 7f3abdfe..d905ae6e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -76,7 +76,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
@@ -84,14 +88,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/intel-vaapi-driver/issues/new) so we all get visibility
+issue in github](https://github.com/intel/intel-vaapi-driver/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
-[Intel vaapi driver waffle.io kanban](https://waffle.io/01org/intel-vaapi-driver).
+[Intel vaapi driver waffle.io kanban](https://waffle.io/intel/intel-vaapi-driver).
## Closing issues
diff --git a/README.md b/README.md
index e6b2b6e3..09eb4cee 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
-[![Stories in Ready](https://badge.waffle.io/01org/intel-vaapi-driver.png?label=ready&title=Ready)](http://waffle.io/01org/intel-vaapi-driver)
-[![Build Status](https://travis-ci.org/01org/intel-vaapi-driver.svg?branch=master)](https://travis-ci.org/01org/intel-vaapi-driver)
-[![Coverity Scan Build Status](https://scan.coverity.com/projects/11612/badge.svg)](https://scan.coverity.com/projects/01org-intel-vaapi-driver)
+[![Stories in Ready](https://badge.waffle.io/intel/intel-vaapi-driver.png?label=ready&title=Ready)](http://waffle.io/intel/intel-vaapi-driver)
+[![Build Status](https://travis-ci.org/intel/intel-vaapi-driver.svg?branch=master)](https://travis-ci.org/intel/intel-vaapi-driver)
+[![Coverity Scan Build Status](https://scan.coverity.com/projects/11612/badge.svg)](https://scan.coverity.com/projects/intel-intel-vaapi-driver)
#Intel-vaapi-driver Project
@@ -17,10 +17,10 @@ commands to be sent to the i915 driver for exercising both hardware and shader f
decode, encode, and processing.
If you would like to contribute to intel-vaapi-driver, check our [Contributing
-guide](https://github.com/01org/intel-vaapi-driver/blob/master/CONTRIBUTING.md).
+guide](https://github.com/intel/intel-vaapi-driver/blob/master/CONTRIBUTING.md).
We also recommend taking a look at the ['janitorial'
-bugs](https://github.com/01org/intel-vaapi-driver/issues?q=is%3Aopen+is%3Aissue+label%3AJanitorial)
+bugs](https://github.com/intel/intel-vaapi-driver/issues?q=is%3Aopen+is%3Aissue+label%3AJanitorial)
in our list of open issues as these bugs can be solved without an
extensive knowledge of intel-vaapi-driver.
diff --git a/configure.ac b/configure.ac
index 9a44c519..795d36ab 100644
--- a/configure.ac
+++ b/configure.ac
@@ -22,9 +22,9 @@ m4_define([wayland_api_version], [1.11.0])
AC_PREREQ([2.57])
AC_INIT([intel_vaapi_driver],
[intel_vaapi_driver_version],
- [https://github.com/01org/intel-vaapi-driver/issues/new],
+ [https://github.com/intel/intel-vaapi-driver/issues/new],
[intel-vaapi-driver],
- [https://github.com/01org/intel-vaapi-driver])
+ [https://github.com/intel/intel-vaapi-driver])
AC_CONFIG_SRCDIR([Makefile.am])
AM_INIT_AUTOMAKE([1.9 tar-ustar -Wno-portability foreign])