docs: Added CHANGELOG & code of conduct before first release candidate. (thanos-io#340)

Signed-off-by: Bartek Plotka <bwplotka@gmail.com>

Author: bwplotka

CHANGELOG.md

@@ -0,0 +1,33 @@
+# Changelog
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
+and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
+
+## Unreleased
+
+Release candidate: [v0.1.0-rc.0](https://github.com/improbable-eng/thanos/releases/tag/v0.1.0-rc.0)
+
+### Added
+- Gossip layer for all components.
+- StoreAPI gRPC proto.
+- TSDB block upload logic for Sidecar.
+- StoreAPI logic for Sidecar.
+- Config and rule reloader logic for Sidecar.
+- On-the fly result merge and deduplication logic for Querier.
+- Custom Thanos UI (based mainly on Prometheus UI) for Querier.
+- StoreAPI logic for Store.
+- Optimized object storage fetch logic for Store.
+- Index cache and chunk pool for Store for better memory usage.
+- Stable support for Google Cloud Storage object storage.
+- StoreAPI logic for Querier to support Thanos federation (experimental).
+- Support for S3 minio-based AWS object storage (experimental).
+- Compaction logic of blocks from multiple sources for Compactor.
+- Downsampling logic for Compactor (experimental).
+- Rule (including alerts) evaluation logic for Ruler (experimental).
+- StoreAPI logic for Ruler.
+- Basic metric orchestration for all components.
+- Verify commands with potential fixes (experimental).
+- Compact / Downsample offline commands.
+- Bucket commands.
+

CODE_OF_CONDUCT.md

@@ -0,0 +1,64 @@
+# 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 members (e.g @bplotka @domgreen, @Fabian Reinartz) at Thanos slack workspace.
+The project team will review and investigate all complaints,
+and will respond in a way that it deems 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/