Epic Goal

• Prepare Observatorium to become a community-driven and open source project, not just a public one.
• At the end of this epic, a community member interested in cloud native technology should be able to discover Observatorium, understand the goals of the project, understand how it works, understand how to contribute, and understand how to use it.

Why is this important?

• We want to leverage the power of the open source community to help develop Observatorium.
• We know that our colleagues working in Cortex, Grafana, Prometheus, etc want to build something like Observatorium and should put the project in a state where it's possible for them to contribute, rather than having to reinvent the wheel.
• If the project is not discoverable and understandable, users will not adopt it, test it, report issues, and otherwise help us improve the stack.

Scenarios

1. A user of CNCF projects stumbles upon a link to observatorium.io; they should find resources that explain the project in terms they understand and should know how to test the project.
2. A contributor to CNCF projects finds the Observatorium GitHub organization; they should understand the repository structures and know how to contribute.

Acceptance Criteria

• The GitHub organization contains a main repository named "observatorium" that contains documentation, deployment configuration, and website content
• The current "observatorium" repository is renamed to "api"
• Navigating to https://observatorium.io produces a non error result containing at least a link to the GitHub; currently only HTTP works and redirects to GitHub; supporting HTTPS is table stakes.
• All active repositories contain CONTRIBUTING.md and CODE_OF_CONDUCT.md files.

Dependencies (internal and external)

Previous Work (Optional)

Open questions

1. What website/documentation generator should we use?

Done Checklist

• Navigating to https://observatorium.io (with TLS) returns HTML containing at least a link to the GitHub