chore: initial project setup

Add GitHub Actions workflow to validate Rusts This includes checking code formatting with `cargo fmt`, linting with `cargo clippy`, and running tests with `cargo test`.
The workflow uses matcher definitions for Cargo error output to improve
the error display in the GitHub Actions log output. It also uses a
Rust actions cache to speed up subsequent workflow runs.

Additionally, this commit adds a basic `.gitignore` file, a
`CODE_OF_CONDUCT.md`, `CONTRIBUTING.md` documentation file with
contribution guidelines, and a `SECURITY.md` file with vulnerability
reporting instructions.

Author: orlandohohmeier

.github/matcher/cargo.json

@@ -0,0 +1,21 @@
+{
+  "problemMatcher": [
+    {
+      "owner": "Cargo (Rust)",
+      "pattern": [
+        {
+          "regexp": "^(warning|warn|error)(\\[(.*)\\])?: (.*)$",
+          "severity": 1,
+          "message": 4,
+          "code": 3
+        },
+        {
+          "regexp": "^([\\s\\->=]*(.*):(\\d*):(\\d*)|.*)$",
+          "file": 2,
+          "line": 3,
+          "column": 4
+        }
+      ]
+    }
+  ]
+}

.github/workflows/validate.yaml

@@ -0,0 +1,36 @@
+name: Validate
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+
+concurrency:
+  group: validate-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+env:
+  CARGO_TERM_COLOR: always
+  CARGO_INCREMENTAL: 0
+  RUST_BACKTRACE: 1
+
+jobs:
+  validate:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 #v4.2.2
+      - uses: swatinem/rust-cache@f0deed1e0edfc6a9be95417288c0e1099b1eeec3 # v2
+        with:
+          save-if: ${{ github.ref == 'refs/heads/main' }}
+          cache-provider: "github"
+      - run: echo "::add-matcher::.github/matcher/cargo.json"
+      - name: Check formatting
+        run: cargo fmt --check
+      - name: Lint
+        run: cargo clippy
+      - name: Test
+        run: cargo test

.gitignore

@@ -0,0 +1 @@
+/target

CODE_OF_CONDUCT.md

@@ -0,0 +1,134 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* 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
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+<!-- TODO: Insert contact method -->
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at `community@katulu.io`.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,183 @@
+# Contributing
+
+This guide will help you understand the overall organization of the project. It's the single source of truth for how to contribute to the code base.
+
+> [!TIP]
+> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD","SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119).
+
+## Setup
+
+<!-- Setup rust  -->
+
+## Components
+
+> [!IMPORTANT]
+> We will probably split this mono-repo into multiple ones to separate the different components and their responsibilities better, allow for easier maintenance and development, as well as ease license handling.
+
+The project is organized into multiple components (crates), each with its own purpose and responsibilities.
+
+```mermaid
+flowchart RL
+    classDef transparent opacity:0
+
+    TODO["TODO: Add component overview"]
+```
+
+<!-- TODO: Add short overview describing the main components purpose. -->
+
+### Adding Components
+
+New components SHOULD be added using `cargo new crates/${NAME}`. This will create a new crate directory with the standard Rust project structure.
+
+After creating a new crate, you MUST link the appropriate license:
+
+```sh
+ln -s LICENSE-${TYPE} crates/${NAME}/LICENSE-${TYPE}
+```
+
+Where `${TYPE}` refers to the license type (e.g., `APACHE` for Apache-2.0).
+
+Make sure to also update the license metadata in each crate's `Cargo.toml` file to correctly reflect the license being used:
+
+```toml
+[package]
+# Other package metadata...
+license = "${TYPE}"
+```
+
+The default license is Apache-2.0, but the project uses multiple licenses for the time being. If you're uncertain about which license to use, please consult the project lead. Make sure to use the SPDF license identifier, see  https://spdx.org/licenses/ for more information.
+
+### Adding Dependencies
+
+When adding dependencies, these MUST be added to the respective crate's `Cargo.toml` file. You can add dependencies using:
+
+```sh
+cargo add ${DEPENDENCY_NAME}
+```
+
+Make sure that the dependency is compatible with the project's licenses.
+
+## Upgrade Dependencies
+
+All dependencies SHALL be updated regularly to maintain an up to date and secure product. Updates SHOULD consider backward compatibility and MUST document compatibility issues.
+
+<!-- TODO: Setup dependabot for automatic dependency updates and security updates and document configuration. -->
+
+## Version Control
+
+Changes SHOULD be committed frequently in small logical chunks that MUST be consistent, work independently of any later commits, and pass the linter plus the tests. Doing so eases rollback and rebase operations. Commits MUST not include any customer data.
+
+Commit message SHALL follow the guidelines stated here, as they provide a framework to write explicit messages that are easy to comprehend when looking through the project history and enable automatic changelog generation. Commit messages MUST never include references to individual customer.
+
+The Guidelines are based on
+[AngularJS Git Commit Message Conventions](https://goo.gl/27wkkO).
+
+This project uses `commitlint` to ensure that messages follow the guidelines.
+Run `yarn install` in the project root to install the respective git hooks.
+
+### Commit-Message
+
+Each commit message MUST consist of a header (type, subject), a body
+and a footer separated by empty lines:
+
+```
+<type>: <subject>
+
+<message>
+
+<footer>
+```
+
+Any line of the commit message MUST NOT be longer than 100 characters to ensure
+that the messages are easy to read.
+
+#### Subject
+
+The subject contains a succinct description of the change. It SHOULD use the
+imperative and present tense; “change” not “changed” nor “changes”.
+The first letter SHALL NOT be capitalized, and MUST NOT end it with a dot.
+
+#### Type
+
+The following commit types are allowed:
+
+- **feat** -
+  use this type for commits that introduce new features or capabilities
+- **fix** - use this one for bug fixes
+- **docs** - use this one to indicate documentation adjustments and improvements
+- **refactor** -
+  use this type for adjustments to improve maintainability or performance
+- **test** - use this one for commits that add missing tests
+- **chore** - use this type for _maintainance_ commits e.g. removing old files
+- **ci** - use this type for CI adjustments
+- **style** - use this one for commits that fix formatting and linting errors
+
+#### Message
+
+The message SHOULD describe the motivation for the change and contrast it with previous behavior. It SHOULD use the imperative and present tense.
+
+#### Referencing Issues
+
+Closed issues MUST be listed on a separate line in the footer prefixed with
+"Closes" keyword.
+
+#### Breaking Changes
+
+All breaking changes MUST be mentioned in the footer with the description of
+the change, justification, and migration notes. Start the block explaining the
+breaking changes with the words `BREAKING CHANGE:` followed by a space.
+
+### Examples
+
+```
+fix: remove UI log statements
+
+Remove console log statements to prevent IE4 errors.
+
+Closes #123, #456
+```
+
+```
+fix: gracefully handle HTTP connections
+
+Gracefully handle 4xx and 5xx status codes to allow for retries when applicable.
+
+Closes #123
+```
+
+```
+feat: add new Graphana data sources
+
+Introduce a new Graphana data source
+
+Closes #123
+```
+
+```
+refactor: change constant names
+
+Adjust constant names, following the new naming conventions.
+
+Closes #123
+```
+
+```
+refactor: simplify video control interface
+
+Simplify the video player control interface as the current
+interface is somewhat hard to use and caused bugs due
+to accidental misuse.
+
+BREAKING CHANGE: VideoPlayer control interface has changed
+to simplify the general usage.
+
+To migrate the code follow the example below:
+
+Before:
+
+VideoPlayer.prototype.stop({pause:true})
+
+After:
+
+VideoPlayer.prototype.pause()
+```