add readme and logos

Author: mjudeikis

CONTRIBUTING.md

@@ -0,0 +1,16 @@
+# Contributing to kcp
+
+We're thrilled that you're interested in contributing to kcp! Please visit our
+[full contributing guide](https://docs.kcp.io/kcp/main/en/CONTRIBUTING/) on our documentation site.
+
+Beside that, what coverns the project and all contributions to it must follow
+the [KCP Project Governance](./GOVERNANCE.md).
+
+From the KCP Project Governance, the following manifesto should guide the technical
+decisions through-out all contributions:
+
+> kcp maintainers strive to be good citizens in the Kubernetes project.
+> kcp maintainers see kcp always as part of the Kubernetes ecosystem and always strive to keep that ecosystem united. In particular, this means:
+> - kcp strives to not divert from Kubernetes, but strives to extend its use-cases to non-container control planes while keeping the ecosystems of libraries and tooling united.
+> - kcp – as a consumer of Kubernetes API Machinery – will strive to stay 100% compatible with the semantics of Kubernetes APIs, while removing container orchestration specific functionality.
+> - kcp strives to upstream changes to Kubernetes code as much as possible.

README.md

@@ -1,16 +1,56 @@
-# Generic Control Plane
+# <img alt="Logo" width="80px" src="./contrib/logo/blue-green.png" style="vertical-align: middle;" /> Generic Control Plane
 
-Generic Control Plane is a Kubernetes API Server flavor that is designed to be used in a standalone mode. It is a lightweight control plane that can be used for development, testing, and learning purposes.
+## Overview
 
-It has all the core components of a Kubernetes control plane without container primitives.
+Generic Control plane (gcp) is a Kubernetes control plane focusing on:
 
-## Usage
+- A **control plane** for Kubernetes-native APIs that can be used **without Kubernetes**
+- Enabling API service providers to **offer APIs centrally**
 
-```
-# Build the control plane
-make
-# Get all the options
-./bin/gcp start options
-# Start the control plane
+gcp can be a building block for SaaS service providers who need a robust API base platform out-of-the-box.
+The goal is to be useful to cloud providers as well as enterprise IT departments offering APIs within their company.
+
+## Documentation
+
+To get started with gcp:
+
+```bash
+# Clone the repository
+git clone https://github.com/kcp-dev/generic-controlplane.git
+
+# Build the project
+cd generic-controlplane && make build
+
+# Start standalone gcp
 ./bin/gcp start
+
+# Access the gcp API
+export KUBECONFIG=.gcp/admin.kubeconfig
+
+# Check resources in the gcp API
+kubectl api-resources
 ```
+
+## Contributing
+
+We ❤️ our contributors! If you're interested in helping us out, please check out [contributing to gcp](CONTRIBUTING.md).
+
+This community has a [Code of Conduct](./code-of-conduct.md). Please make sure to follow it.
+
+## Getting in touch
+
+There are several ways to communicate with us:
+
+- The [`#kcp-dev` channel](https://app.slack.com/client/T09NY5SBT/C021U8WSAFK) in the [Kubernetes Slack workspace](https://slack.k8s.io).
+- Our mailing lists:
+    - [kcp-dev](https://groups.google.com/g/kcp-dev) for development discussions.
+    - [kcp-users](https://groups.google.com/g/kcp-users) for discussions among users and potential users.
+- By joining the kcp-dev mailing list, you should receive an invite to our bi-weekly community meetings.
+- See recordings of past community meetings on [YouTube](https://www.youtube.com/channel/UCfP_yS5uYix0ppSbm2ltS5Q).
+- The next community meeting dates are available via our [CNCF community group](https://community.cncf.io/kcp/).
+- Check the [community meeting notes document](https://docs.google.com/document/d/1PrEhbmq1WfxFv1fTikDBZzXEIJkUWVHdqDFxaY1Ply4) for future and past meeting agendas.
+- Browse the [shared Google Drive](https://drive.google.com/drive/folders/1FN7AZ_Q1CQor6eK0gpuKwdGFNwYI517M?usp=sharing) to share design docs, notes, etc.
+    - Members of the kcp-dev mailing list can view this drive.
+
+## License
+[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Fkcp-dev%2Fkcp.svg?type=large)](https://app.fossa.com/projects/git%2Bgithub.com%2Fkcp-dev%2Fkcp?ref=badge_large)

code-of-conduct.md

@@ -0,0 +1,83 @@
+This project is following the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md).
+
+# Community Code of Conduct
+
+As contributors, maintainers, and participants in the CNCF community, and in the interest of fostering
+an open and welcoming community, we pledge to respect all people who participate or contribute
+through reporting issues, posting feature requests, updating documentation,
+submitting pull requests or patches, attending conferences or events, or engaging in other community or project activities.
+
+We are committed to making participation in the CNCF community a harassment-free experience for everyone, regardless of age, body size, caste, disability, ethnicity, level of experience, family status, gender, gender identity and expression, marital status, military or veteran status, nationality, personal appearance, race, religion, sexual orientation, socieconomic status, tribe, or any other dimension of diversity.
+
+## Scope
+
+This code of conduct applies:
+* within project and community spaces,
+* in other spaces when an individual CNCF community participant's words or actions are directed at or are about a CNCF project, the CNCF community, or another CNCF community participant.
+
+### CNCF Events
+
+CNCF events that are produced by the Linux Foundation with professional events staff are governed by the Linux Foundation [Events Code of Conduct](https://events.linuxfoundation.org/code-of-conduct/) available on the event page. This is designed to be used in conjunction with the CNCF Code of Conduct.
+
+## Our Standards
+
+The CNCF Community is open, inclusive and respectful. Every member of our community has the right to have their identity respected.
+
+Examples of behavior that contributes to a positive environment include but are not limited to:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+* Using welcoming and inclusive language
+
+
+Examples of unacceptable behavior include but are not limited to:
+
+* The use of sexualized language or imagery
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment in any form
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Violence, threatening violence, or encouraging others to engage in violent behavior
+* Stalking or following someone without their consent
+* Unwelcome physical contact
+* Unwelcome sexual or romantic attention or advances
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+The following behaviors are also prohibited:
+* Providing knowingly false or misleading information in connection with a Code of Conduct investigation or otherwise intentionally tampering with an investigation.
+* Retaliating against a person because they reported an incident or provided information about an incident as a witness.
+
+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 a CNCF project.
+Project maintainers who do not follow or enforce the Code of Conduct may be temporarily or permanently removed from the project team.
+
+## Reporting
+
+For incidents occurring in the Kubernetes community, contact the [Kubernetes Code of Conduct Committee](https://git.k8s.io/community/committee-code-of-conduct) via <conduct@kubernetes.io>. You can expect a response within three business days.
+
+For other projects, or for incidents that are project-agnostic or impact multiple CNCF projects, please contact the [CNCF Code of Conduct Committee](https://www.cncf.io/conduct/committee/) via conduct@cncf.io.  Alternatively, you can contact any of the individual members of the [CNCF Code of Conduct Committee](https://www.cncf.io/conduct/committee/) to submit your report. For more detailed instructions on how to submit a report, including how to submit a report anonymously, please see our [Incident Resolution Procedures](https://www.cncf.io/conduct/procedures/). You can expect a response within three business days.
+
+For incidents ocurring at CNCF event that is produced by the Linux Foundation, please contact eventconduct@cncf.io.
+
+## Enforcement
+
+Upon review and investigation of a reported incident, the CoC response team that has jurisdiction will determine what action is appropriate based on this Code of Conduct and its related documentation.
+
+For information about which Code of Conduct incidents are handled by project leadership, which incidents are handled by the CNCF Code of Conduct Committee, and which incidents are handled by the Linux Foundation (including its events team), see our [Jurisdiction Policy](https://www.cncf.io/conduct/jurisdiction/).
+
+## Amendments
+
+Consistent with the CNCF Charter, any substantive changes to this Code of Conduct must be approved by the Technical Oversight Committee.
+
+## Acknowledgements
+
+This Code of Conduct is adapted from the Contributor Covenant
+(http://contributor-covenant.org), version 2.0 available at
+http://contributor-covenant.org/version/2/0/code_of_conduct/

contrib/logo/README.md

@@ -0,0 +1,36 @@
+# KCP Logo
+
+The logo of KCP is a hypercube, viewed symmetrically in a way that it forms two 
+nested, equally oriented, centered regular hexagons with the connecting hypercube 
+lines clearly visible, either through color contrast or a line.
+
+There are these variants, to be used depending on context:
+
+1. normal <img alt="Logo" width="198px" align="right" src="./blue-green.png"/><br clear="right"/>
+1. high contrast <img alt="Logo" width="210px" align="right" src="./blue-green-high-contrast.png"/><br clear="right"/>
+2. glow <img alt="Logo" width="205px" align="right" src="./blue-green-glow.png"/><br clear="right"/>
+
+Moreover, there is a red-blue variant: 
+1. normal <img alt="Logo" width="198px" align="right" src="./red-blue.png"/><br clear="right"/>
+2. high contrast <img alt="Logo" width="210px" align="right" src="./red-blue-high-contrast.png"/><br clear="right"/>
+3. glow <img alt="Logo" width="205px" align="right" src="./red-blue-glow.png"/><br clear="right"/>
+
+Depending on context one or the other variant makes more sense visually.
+
+The KCP font is [Ubuntu](https://fonts.google.com/specimen/Ubuntu).
+
+The application used for the original files is [Amadine](https://amadine.com/).
+
+## Copyright 2022 The KCP Authors.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.