summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authork8s-ci-robot <k8s-ci-robot@users.noreply.github.com>2018-02-19 21:26:38 -0800
committerGitHub <noreply@github.com>2018-02-19 21:26:38 -0800
commit94a104dcf3b74f5b3c2ea40eb075aff52fffd754 (patch)
tree36c8736188e3e6a15d89fac76f17f41b9c82bd3b
parent25b16c973e436e3e89f6d164407d419d2ea20e27 (diff)
parent0b774ed796fc0a3af49b4e714ae91668ba9cde95 (diff)
Merge pull request #1778 from cblecker/godeps-owners
Add section on reviewing/approving godeps
-rw-r--r--contributors/devel/godep.md22
1 files changed, 22 insertions, 0 deletions
diff --git a/contributors/devel/godep.md b/contributors/devel/godep.md
index c997a1ca..36856aa2 100644
--- a/contributors/devel/godep.md
+++ b/contributors/devel/godep.md
@@ -187,3 +187,25 @@ paths to coexist in the same git repo.
The verifiers, including `hack/verify-godeps.sh` *must* pass for every pull
request.
+
+## Reviewing and approving dependency changes
+
+Particular attention to detail should be exercised when reviewing and approving
+PRs that add/remove/update dependencies. Importing a new dependency should bring
+a certain degree of value as there is a maintenance overhead for maintaining
+dependencies into the future.
+
+When importing a new dependency, be sure to keep an eye out for the following:
+- Is the dependency maintained?
+- Does the dependency bring value to the project? Could this be done without
+ adding a new dependency?
+- Is the target dependency the original source, or a fork?
+- Is there already a dependency in the project that does something similar?
+- Does the dependency have a license that is compatible with the Kubernetes
+ project?
+
+All new dependency licenses should be reviewed by either Tim Hockin (@thockin)
+or the Steering Committee (@kubernetes/steering-committee) to ensure that they
+are compatible with the Kubernetes project license. It is also important to note
+and flag if a license has changed when updating a dependency, so that these can
+also be reviewed.