Added guidelines and devcontainer for our opensource project

Author: Thomas Luijken

.devcontainer/Dockerfile

@@ -0,0 +1,15 @@
+FROM jetpackio/devbox:latest
+
+# Installing your devbox project
+WORKDIR /code
+USER root:root
+RUN mkdir -p /code && chown ${DEVBOX_USER}:${DEVBOX_USER} /code
+USER ${DEVBOX_USER}:${DEVBOX_USER}
+COPY --chown=${DEVBOX_USER}:${DEVBOX_USER} devbox.json devbox.json
+COPY --chown=${DEVBOX_USER}:${DEVBOX_USER} devbox.lock devbox.lock
+
+
+
+RUN devbox run -- echo "Installed Packages."
+
+RUN devbox shellenv --init-hook >> ~/.profile

.devcontainer/devcontainer.json

@@ -0,0 +1,16 @@
+{
+  "name": "Devbox Remote Container",
+  "build": {
+    "dockerfile": "./Dockerfile",
+    "context": ".."
+  },
+  "customizations": {
+    "vscode": {
+      "settings": {},
+      "extensions": [
+        "jetpack-io.devbox"
+      ]
+    }
+  },
+  "remoteUser": "devbox"
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# 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 [hello@baseflow.com](mailto:hello@baseflow.com). 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/

CONTRIBUTE.md

@@ -0,0 +1,96 @@
+Contributing to Oxybox
+-----
+
+## What You'll Need
+
+  * **Git**: Essential for version control. You can find installation instructions [here](https://git-scm.com/).
+  * **A GitHub Account**: If you don't have one, you can sign up for free [here](https://github.com/).
+
+-----
+
+## Getting Started with Your Development Environment
+
+To make setup as smooth as possible, you have a few options for your development environment:
+
+  * **Devbox**: This is a pre-configured development environment that ensures you have all the necessary tools and dependencies readily available. [Link to Devbox setup instructions]
+  * **Devcontainer**: If you use VS Code or another IDE that supports Devcontainers, you can get up and running quickly with a consistent environment.
+
+If you prefer to set up your environment manually, follow these steps:
+
+1.  **Fork the Repository**: Go to `https://github.com/baseflow/oxybox` and fork the repository to your personal GitHub account.
+2.  **Clone Your Fork**: On your local machine, clone your forked repository:
+    ```bash
+    git clone git@github.com:<your_name_here>/oxybox.git
+    ```
+3.  **Navigate to the Project Directory**:
+    ```bash
+    cd oxybox
+    ```
+4.  **Add Upstream Remote**: To keep your fork synchronized with the original Oxybox repository, add it as an upstream remote:
+    ```bash
+    git remote add upstream https://github.com/baseflow/oxybox.git
+    ```
+
+-----
+
+## Contributing to Oxybox
+
+We highly appreciate contributions via GitHub pull requests\! Here's how to contribute:
+
+1.  **Sync with Upstream**: Before you start, make sure your local `main` branch is up-to-date with the latest changes from the original repository:
+
+    ```bash
+    git fetch upstream
+    git checkout main
+    git merge upstream/main
+    ```
+
+2.  **Create a New Branch**: Create a new branch for your changes. Use a descriptive name that reflects the purpose of your contribution:
+
+    ```bash
+    git checkout -b <your-feature-or-fix-branch-name>
+    ```
+
+3.  **Make Your Changes**: Implement your features or bug fixes.
+
+4.  **Test Your Changes**: Since Oxybox is written in Rust, you'll want to run tests to ensure your changes haven't introduced any regressions and work as expected.
+
+    ```bash
+    cargo test
+    ```
+
+5.  **Format Your Code**: Ensure your code adheres to the project's formatting standards:
+
+    ```bash
+    cargo fmt
+    ```
+
+6.  **Lint Your Code**: Run clippy to catch common mistakes and improve code quality:
+
+    ```bash
+    cargo clippy
+    ```
+
+7.  **Commit Your Changes**: Stage and commit your changes with a clear and concise commit message:
+
+    ```bash
+    git add .
+    git commit -m "feat: Add a concise description of your changes"
+    ```
+
+    (Replace "feat:" with "fix:", "docs:", "refactor:", etc., as appropriate following conventional commits.)
+
+8.  **Push to Your Fork**: Push your new branch to your forked repository on GitHub:
+
+    ```bash
+    git push origin <your-feature-or-fix-branch-name>
+    ```
+
+9.  **Create a Pull Request**: Go to the Oxybox repository on GitHub (`https://github.com/baseflow/oxybox`) and click the "Compare & pull request" button.
+
+    Please ensure you:
+
+      * Fill out the pull request template completely.
+      * Address any warnings or errors reported by `cargo clippy` and `cargo test`.
+
+We're excited to see your contributions\!

LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Baseflow
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.