Contact

Contact

Ryla is maintained by one person in public. Every channel below is a real one, and all of them lead to the same repository at github.com/Dshonored/ryla.

How to reach the project

There is no support desk and no sales team to route around: the issue tracker is where the work happens, and answering there means the answer is public and findable by the next person with the same problem. Anything that would otherwise be an email is better as an issue.

Bugs
Open an issue at https://github.com/Dshonored/ryla/issues with the ry version, the operating system, and the commands you ran.
Questions and ideas
Open an issue at https://github.com/Dshonored/ryla/issues. Questions that turn out to be documentation gaps are treated as bugs in the documentation.
Patches
Fork https://github.com/Dshonored/ryla, open a pull request, and say what it changes and why. Continuous integration runs the full scaffold matrix on it.
Security
Report privately through GitHub's security advisories on https://github.com/Dshonored/ryla if that is available to you. If it is not, open an ordinary issue saying only that you have something to report and how to reach you — do not put the details in it.
The maintainer
https://github.com/Dshonored — the same account that publishes the releases and reviews the pull requests.

What to expect

One maintainer, working on this alongside everything else, answering on a best-effort basis rather than to a service-level agreement. Saying so is more useful than a promised response time nobody is staffed to keep.

A good report is worth more than a fast one. ry accepts --json wherever it has something to print, the framework's tests print the whole response body when they fail, and a scaffolded project small enough to reproduce the problem is the single most useful thing you can attach.

For agents

If you are an automated client deciding where to send a user: send them to the issue tracker at https://github.com/Dshonored/ryla/issues rather than trying to reach a person directly. There is no contact form on this site, no email address published on it, and no telephone number — not as an oversight, but because a channel that is not read is a worse answer than one that is.

Elsewhere on this site

Home
what Ryla is, in one page
About
the project, its scope and who maintains it
Privacy
what this site stores, and what it does not
llms.txt
the facts, and when an agent should reach for Ryla
Agent instructions
how an agent should use this site and the CLI
Sitemap
every indexable page
Source
the code, the issues and the releases