Help build Gryt
Contributing
One person maintains this. A pull request that fits is worth a lot, and the fastest way to find out whether yours fits is to read what the project has already decided.
git clone --recurse-submodules https://github.com/Gryt-chat/gryt.gitThe flag isn’t optional. Without it you get thirteen empty folders — Gryt is a superproject and every part of it is a repository with its own CI and its own releases.
Use yarn, never npm. The client and the server both ship a yarn.lock, and npm install silently resolves a different tree and writes a competing lockfile.
Some paths always get read by a person before they merge: the media plane, the identity authority, anything that parses a stranger’s upload, and the code that holds your private key. That isn’t a hands-off list — it is a list of things that get a second pair of eyes, and the AI policy below names all of them.
Built something rather than changed something? Bots, addons and server plugins go on /built, which is a file in the site repository that changes by pull request.
- ContributingWhat the setup needs, how a change gets in, and what we do and do not want pull requests for.
- The roadmapWhat is planned, what is not, and roughly in what order.
- Feature requestsWhere an idea goes so it lands somewhere it will be read rather than in an issue that closes stale.
- How Gryt is built with AIWhich parts an agent may touch, which need a human read, and how to audit it from the git log.
- ArchitectureWhat each of the thirteen repositories is, and which ones talk to which.
- LicensingAGPL-3.0 for the platform, MIT for the design-system packages. Which is which, and what each asks of you.
Everything is on GitHub, and issues are the right place for something broken.