Stash

A public playground for small experiments, useful tools, and ideas worth keeping. Maintained by Joe Amditis on the Inference Cooperative’s Gitea.

Stash gives unfinished ideas room to become useful. Each experiment should explain what it does, how to try it, and what remains uncertain. This repository starts with the project scaffolding; no applications or hosted demos are included yet.

Start here

• Browse the experiment index.
• Read the contribution guide before adding something.
• Use issues for ideas and reproducible problems.
• Submit changes through a pull request.

Get a local copy

git clone https://git.inference.coop/jamditis/stash.git
cd stash
git switch -c experiment/your-idea

There is no repository-wide install or build step. Each future experiment should document its own dependencies and commands. Browser sign-in does not configure terminal Git authentication.

Keep experiments self-contained

Use a short, descriptive directory name under experiments/ when adding a project. Include a README with its purpose, status, setup, usage, checks, limitations, and sources or license notices. Add an entry to the experiment index so people can find it. Keep dependencies and generated output scoped to that project.

Suggested statuses: idea, prototype, usable, or archived. Label examples and mock data clearly. A successful demo is not evidence of production readiness.

Working together

Small, focused changes are easier to review. Describe what changed and why, include screenshots for visual work, and record the checks you actually ran. Draft pull requests are welcome for unfinished work. See CONTRIBUTING.md for the checklist.

Public by design

Everything committed here is public. Use synthetic or explicitly approved public data. Keep credentials, personal archives, private correspondence, and internal work files out of commits and issues. The ignore rules are a convenience, not a security boundary. Review the staged diff before pushing.

Checks and automation

This starter has no runtime dependencies and no automated CI configured. Issue and pull-request templates help document verification. Add CI alongside a real experiment once its commands and the co-op’s runner availability are confirmed.

License

Original contributions to this repository use Apache-2.0. Retain notices and applicable licenses for any third-party material; do not assume this license covers imported content.