Update template files to include repo-specific info

CONTRIBUTING.md

@@ -20,12 +20,7 @@ If your repo has certain guidelines for contribution, put them here ahead of the
 
 - [Mentoring Initiatives](https://git.k8s.io/community/mentoring) - We have a diverse set of mentorship programs available that are always looking for volunteers!
 
-<!---
-Custom Information - if you're copying this template for the first time you can add custom content here, for example:
-
 ## Contact Information
 
-- [Slack channel](https://kubernetes.slack.com/messages/kubernetes-users) - Replace `kubernetes-users` with your slack channel string, this will send users directly to your channel. 
+- [Slack](https://kubernetes.slack.com/messages/sig-storage)
-- [Mailing list](URL)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-storage)
-
--->

OWNERS

@@ -1,6 +1,5 @@
 # See the OWNERS docs at https://go.k8s.io/owners
 
 approvers:
-  # TODO: in your repo created from this template, you should replace the
+  - wongma7
-  # steering-committee with a list of project owners, see the doc linked above.
+  - jsafrane
-  - steering-committee

OWNERS_ALIASES

@@ -1,15 +0,0 @@
-# See the OWNERS docs at https://go.k8s.io/owners#owners_aliases
-
-aliases:
-  # TODO: remove this alias, it will go stale in your repo, and in your repo
-  # you should have your own set of approvers (see OWNERS)
-  # in the original template repo, we must maintain this list to approve changes
-  # to the template itself
-  steering-committee:
-    - cblecker
-    - derekwaynecarr
-    - dims
-    - nikhita
-    - parispittman
-    - spiffxp
-    - timothysc

README.md

@@ -1,16 +1,6 @@
-# Kubernetes Template Project
+# nfs-subdir-external-provisioner
 
-The Kubernetes Template Project is a template for starting new projects in the GitHub organizations owned by Kubernetes. All Kubernetes projects, at minimum, must have the following files:
+Dynamic sub-dir volume provisioner on a remote NFS server.
-
-- a `README.md` outlining the project goals, sponsoring sig, and community contact information
-- an `OWNERS` with the project leads listed as approvers ([docs on `OWNERS` files][owners])
-- a `CONTRIBUTING.md` outlining how to contribute to the project
-- an unmodified copy of `code-of-conduct.md` from this repo, which outlines community behavior and the consequences of breaking the code
-- a `LICENSE` which must be Apache 2.0 for code projects, or [Creative Commons 4.0] for documentation repositories, without any custom content
-- a `SECURITY_CONTACTS` with the contact points for the Product Security Team 
-  to reach out to for triaging and handling of incoming issues. They must agree to abide by the
-  [Embargo Policy](https://git.k8s.io/security/private-distributors-list.md#embargo-policy)
-  and will be removed and replaced if they violate that agreement.
 
 ## Community, discussion, contribution, and support
 
@@ -18,12 +8,9 @@ Learn how to engage with the Kubernetes community on the [community page](http:/
 
 You can reach the maintainers of this project at:
 
-- [Slack](http://slack.k8s.io/)
+- [Slack](https://kubernetes.slack.com/messages/sig-storage)
-- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-dev)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-storage)
 
 ### Code of conduct
 
 Participation in the Kubernetes community is governed by the [Kubernetes Code of Conduct](code-of-conduct.md).
-
-[owners]: https://git.k8s.io/community/contributors/guide/owners.md
-[Creative Commons 4.0]: https://git.k8s.io/website/LICENSE

SECURITY_CONTACTS

@@ -10,5 +10,7 @@
 # DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE
 # INSTRUCTIONS AT https://kubernetes.io/security/
 
-bob
+jsafrane
-alice
+msau42
+saad-ali
+xing-yang