added code of conduct and governance documentation plus a proposal ho…

…w to submit SIG proposals

code-of-conduct.md

@@ -0,0 +1,76 @@
+Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
+
+# Contributor Covenant Code of Conduct
+
+## Our pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

governance.md

@@ -0,0 +1,120 @@
+The Spinnaker OSS project is run by a group of appointed members who hold specific roles, managed by the technical oversight committee. The steering committee manages the governance structure of the project, revisiting and refining it as needs evolve.
+
+The broader community is organized around a set of special interest groups (SIGs) focused on particular areas of interest.
+
+## Roles
+
+To make clearer to community members how they might progressively get more involved and take more ownership in the project, we define the following appointed roles with their respective duties and qualifications.
+
+Roles are appointed by the Technical Oversight Committee (TOC). Roles can be revoked for reasons such as falling out of qualification, inactivity, or for violations of community guidelines.
+
+### Active Community Members
+
+Everyone is a welcome community member! Here are some things that we find extraordinarily helpful:
+
+* Answering questions in our [Slack team](https://spinnakerteam.slack.com/)
+* Answering questions in our [forum](https://community.spinnaker.io/)
+* Leave feedback on PRs - questions, code style, and bug spotting are all helpful
+* Help new developers get started
+* Reproduce bugs and add detail to issues
+* Join a SIG, discuss community issues, and/or lead a SIG
+
+### Reviewers
+
+Duties
+
+* Review, provide meaningful feedback and LGTM PRs
+* Triage GitHub issues, community forum submissions
+* Provide general support in Slack
+
+Qualification guidelines
+
+* Known active participant in the community
+* Has submitted at least 5 PRs of significant scope that are correspondingly merged
+* Sponsored by 2 Approvers
+
+[Current Reviewers](https://github.com/spinnaker/spinnaker/blob/master/reviewers.md)
+
+If you’d like to nominate yourself as a Reviewer, please reach out to the [TOC](#technical-oversight-committee), or 
+self-nominate using [this form](https://docs.google.com/forms/d/e/1FAIpQLScJtnQc4VJNSoZj9JivoMBNzbULDCzpg3IZgp5ScIeeGF1onQ/viewform?usp=sf_link)
+
+### Approvers
+
+Duties
+
+* Final review for PRs
+* Merge code into master
+* All Reviewer duties
+
+Qualification guidelines
+
+* Belongs to an organization with significant stake in project
+* Known active participant in the community
+* Has submitted at least 5 PRs of significant scope that are merged
+* Has reviewed 5 PRs of significant scope
+* Sponsored by 2 Approvers
+
+[Current Approvers](https://github.com/spinnaker/spinnaker/blob/master/approvers.md)
+
+If you’d like to nominate yourself as an Approver, please reach out to the [TOC](#technical-oversight-committee), or
+self-nominate using [this form](https://docs.google.com/forms/d/e/1FAIpQLSfmDfZWTSG2uQ66i9mSD7zuBO59Fg31sNkx47M3KpqlLK_wAg/viewform?usp=sf_link).
+
+### Technical Oversight Committee
+
+The TOC is responsible for the overall technical management of the project, ultimately managing the day-to-day running of the project.
+
+Duties
+
+* Set agenda for, facilitate, and drive consensus in the TOC meetings
+* Final escalation point for technical guidance
+* Review, approve and revoke appointments for Reviewers and Approvers
+* Drive technical management and any specific guidelines (e.g. code requirements/conventions, SLA on PR reviews)
+
+Qualifications
+
+* Nominated by community
+* Appointed by Steering Committee
+
+Logistics
+
+* [Agenda doc](https://docs.google.com/document/d/1PxIA1XE3nzqLykOFW-AqdU5u9F8cFh3jDvUA41P2cUM/edit)
+* Email: [[email protected]](mailto:[email protected])
+
+Current TOC members:
+
+* Adam Jordens (Netflix)
+* Rob Zienert (Netflix)
+* Travis Tomsu (Google)
+
+The technical oversight committee is initially seeded with core members from Netflix and Google. We will leave further details such as number of seats, qualifications, tenure, TBD for the time being.
+
+### Steering Committee
+
+The steering committee’s responsibility and function lies in the continual shaping of the governance structure to serve the project’s needs best.
+
+Duties:
+
+* Set governance structure of the project
+* Address questions or concerns from the community about project culture, structure, and clarifications of roles, responsibilities and duties.
+* Ratify new SIGs
+
+Logistics
+
+* [Agenda doc](https://docs.google.com/document/d/1HMdwvBPM4uRFqoeAd7eEkVWIC8dQP40zFavOE5Kq-Eg/edit)
+* Email: [[email protected]](mailto:[email protected])
+
+Current SC members:
+
+* Andy Glover (Netflix)
+* Matt Duftler (Google)
+* Peter Stout (Netflix)
+* Ruslan Meshenberg (Netflix)
+* Steven Kim (Google)
+
+The steering committee is initially seeded by Netflix and Google as the project matures and its structure stabilizes. We will leave further details such as number of seats, qualifications, tenure, appointing measures, TBD for the time being.
+
+## SIGS
+
+SIGs (special interest groups) are created as community interest and demand around particular topics become self evident, and continue on as their relevance and needs do. SIGs and their leads are ratified and greenlit by the [steering committee](#steering-committee).
+
+[See the SIG list here](/community/governance/sigs).