Merge pull request #66 from mikeshng/update-mission

update mission statement by:

Author: openshift-merge-robot

MISSION.md

@@ -9,7 +9,6 @@ We are initially interested in the following lifecycles associated with expandin
 1. Cluster Lifecycle. How are clusters provisioned, upgraded, registered, scaled out or in and decommissioned?
 2. Policy & Configuration Lifecycle. How are clusters configured, audited, secured, access controlled, managed for quota or cost?
 3. Application Lifecycle. How are containerized or hybrid applications delivered across one or more clusters? How are those applications kept current with ongoing changes?
-4. Observability. How does a user understand the health of their cluster fleet? How does a user understand the health of distributed applications? How does a user search available clusters or applications and diagnose problems when they occur?
 
 Our initial goals for the project are to define API and reference implementations for common use cases that we have observed as users grow their adoption of Kubernetes:
 
@@ -18,14 +17,13 @@ Our initial goals for the project are to define API and reference implementation
 - Define API for dynamic placement of content and behavior across multiple clusters.
 - Define API for policy definition to ensure desired configuration and security settings are auditable or enforceable.
 - Define API for distributed application delivery across many clusters and the ability to deliver ongoing updates.
-- Define API to collect cluster and application health metrics and alerts across multiple clusters.
 
 We expect that over time, the project will make sense to contribute to an appropriate foundation for stewardship. In the meantime, we intend to engage and contribute where similar use cases are under active discussion in the community including the Kubernetes SIG-Multicluster and SIG-Policy workgroups, among others.
 
 ## Contributor Code of Conduct
 The Open Cluster Management project has adopted the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). The English text of the CNCF Code of Conduct is made available here for reference. Additional [language translations](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) are available.
 
-“As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
+"As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
 
 We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.
 Examples of unacceptable behavior by participants include:
@@ -36,8 +34,8 @@ Public or private harassment
 Publishing others' private information, such as physical or electronic addresses, without explicit permission
 Other unethical or unprofessional conduct.
 Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team.
-This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.”
-Instances of abusive, harassing, or otherwise unacceptable behavior in Open Cluster Management may be reported by contacting [NEED POINT OF CONTACT].” [[Reference](https://github.com/cncf/foundation/blob/master/code-of-conduct.md)]
+This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
+Instances of abusive, harassing, or otherwise unacceptable behavior in Open Cluster Management may be reported by contacting `[email protected]`." [[Reference](https://github.com/cncf/foundation/blob/master/code-of-conduct.md)]
 
 ## Getting Involved
 
@@ -54,29 +52,19 @@ Suggested API and implementations will be accepted in accordance with the broad
 To ensure opportunities for broad user contributions, a public forum will be hosted to demonstrate new capabilities, solicit feedback and offer a forum for real time Q&A.
 Meeting recordings will be posted to a YouTube channel for offline viewing.
 
-- Public Agenda (Link TBD)
-- First Monday of the month
-  - 5-6 PM US Pacific / 8-9 PM US Eastern / 1-2 AM GMT / 8-9 AM (Tuesday) China
-- Third Monday of the month
-  - 8-9 AM US Pacific / 11 AM - 12 PM US Eastern / 4-5 PM GMT / 8-9 PM (Monday) China
+The community meets on a bi-weekly cadence on Thursday at 15:30 UTC.
 
-## Community Architecture Forum
-
-Technical discussions will also be held in an open forum. The topics for the Community Architecture Forum will cover technical review of APIs and relevant implementation details.
-Meeting recordings will be posted to a YouTube channel for offline viewing.
-
-
-- Public Agenda (Link TBD)
-- Second Monday of the month
-  - 5-6 PM US Pacific / 8-9 PM US Eastern / 1-2 AM GMT / 8-9 AM (Tuesday) China
-- Fourth Monday of the month
-  - 8-9 AM US Pacific / 11 AM -12 PM US Eastern / 4-5 PM GMT / 8-9 PM (Monday) China
+Meeting Agenda and Topics can be found here: https://github.com/open-cluster-management-io/community/projects/1.
 
 ## Communication
 
-A public [Google Group](https://groups.google.com/g/open-cluster-management) has been created to facilitate offline discussion outside of Github issues or Pull Requests.
+See the following options to connect with the community:
 
-The project team has chosen to defer a new Slack team until we get enough critical mass in the community to warrant joining another Slack team or workspace.
+ - [Website](https://open-cluster-management.io)
+ - [Slack](https://kubernetes.slack.com/archives/C01GE7YSUUF)
+ - [Mailing group](https://groups.google.com/g/open-cluster-management)
+ - [Community meetings](https://github.com/open-cluster-management-io/community#community-meetings)
+ - [YouTube channel](https://www.youtube.com/channel/UC7xxOh2jBM5Jfwt3fsBzOZw)
 
 ## Governance
 
@@ -91,9 +79,8 @@ The project team has chosen to defer a new Slack team until we get enough critic
 
 ## Public Roadmap
 
-
-
+Roadmap is tracked using GitHub project. See https://github.com/open-cluster-management-io/community/projects/2
 
 ## Security Response
 
-Please see https://github.com/open-cluster-management-io/community/blob/master/SECURITY.md.
+Please see https://github.com/open-cluster-management-io/community/blob/master/SECURITY.md.