Merge pull request #24 from chetak123/main

Added README

Author: k8s-ci-robot

README.md

@@ -1,29 +1,61 @@
-# Kubernetes Template Project
-
-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:
-
-- 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
-
-Learn how to engage with the Kubernetes community on the [community page](http://kubernetes.io/community/).
-
-You can reach the maintainers of this project at:
-
-- [Slack](http://slack.k8s.io/)
-- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-dev)
-
-### 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 Special Interest Group
+
+Covers horizontal security initiatives for the Kubernetes project, including regular security audits, the vulnerability management process, cross-cutting security documentation, and security community management.
+
+The [charter](https://github.com/kubernetes/community/blob/master/sig-security/charter.md) defines the scope and governance of the Security Special Interest Group.
+
+## Meetings
+*Joining the [mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-security) for the group will typically add invites for the following meetings to your calendar.*
+* Regular SIG Meeting: [Thursdays at 9:00 PT (Pacific Time)](https://zoom.us/j/9934z1184192?pwd=L25Tc0ZOL3FqU09KNERlTU12dFhTQT09) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:00&tz=PT%20%28Pacific%20Time%29).
+  * [Meeting notes and Agenda](https://docs.google.com/document/d/1GgmmNYN88IZ2v2NBiO3gdU8Riomm0upge_XNVxEYXp0/edit?usp=sharing).
+  * [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP1mXOLAc9ti0oX8s_ookQCi).
+
+## Leadership
+
+### Chairs
+The Chairs of the SIG run operations and processes governing the SIG.
+
+* Ian Coldwater (**[@IanColdwater](https://github.com/IanColdwater)**), Twilio
+* Tabitha Sable (**[@tabbysable](https://github.com/tabbysable)**), Datadog
+
+## Contact
+- Slack: [#sig-security](https://kubernetes.slack.com/messages/sig-security)
+- [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-security)
+- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fsecurity)
+- [Sig Security Issues](https://github.com/kubernetes/sig-security/issues)
+- GitHub Teams:
+    - [@kubernetes/sig-security-leads](https://github.com/orgs/kubernetes/teams/sig-security-leads) - SIG Security Leads
+    - [@kubernetes/sig-security-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-security-pr-reviews) - SIG Security PR review notifications
+- Steering Committee Liaison: Paris Pittman (**[@parispittman](https://github.com/parispittman)**)
+
+## Subprojects
+
+The following [subprojects][subproject-definition] are owned by sig-security:
+### security-assessments
+Information about Security Assessments
+- **Owners:**
+  - [@kubernetes/sig-security-assessments](https://github.com/kubernetes/sig-security/blob/main/sig-security-assessments/OWNERS)
+### security-audit
+Third Party Security Audit
+- **Owners:**
+  - [kubernetes/sig-security/sig-security-external-audit](https://github.com/kubernetes/sig-security/blob/main/sig-security-external-audit/OWNERS)
+### security-docs
+Security Documents and Documentation
+- **Owners:**
+  - [kubernetes/sig-security/sig-security-docs](https://github.com/kubernetes/sig-security/blob/main/sig-security-docs/OWNERS)
+- **Contact:**
+  - Slack: [#sig-security-docs](https://kubernetes.slack.com/messages/sig-security-docs)
+### security-tooling
+Development and Enhancements of Security Tooling
+- **Owners:**
+  - [kubernetes/sig-security/sig-security-tooling](https://github.com/kubernetes/sig-security/blob/main/sig-security-tooling/OWNERS)
+- **Contact:**
+  - Slack: [#sig-security-tooling](https://kubernetes.slack.com/messages/sig-security-tooling)
+### sig-security
+SIG Security discussions, documents, processes and other artifacts
+- **Owners:**
+  - [kubernetes/sig-security](https://github.com/kubernetes/sig-security/blob/master/OWNERS)
+- **Contact:**
+  - Slack: [#sig-security](https://kubernetes.slack.com/messages/sig-security)
+
+[subproject-definition]: https://github.com/kubernetes/community/blob/master/governance.md#subprojects