No public release catalogue
We do not currently have a list of supported public packages to offer. When that changes, the work will appear here with documentation and a clear maintenance status.
Front page
Most of what we build is closed source today. We plan to publish work when it is useful, documented and something we can keep looking after. Until then, this page will not pretend a public backlog is a public codebase.
Most product code and internal tooling are private. That may change piece by piece; it will not change because an empty repository looked good in a profile.
We do not currently have a list of supported public packages to offer. When that changes, the work will appear here with documentation and a clear maintenance status.
The products and the systems used to operate them are largely private today. We are not attaching an “open” label to a screenshot, a roadmap or a folder full of intentions.
Opening code is the start of a job, not the end of an announcement. Three things have to be true before we do it.
We will publish tools that solve a real problem on their own, not scraps separated from the part that made them useful.
A README is the floor. Installation, examples and the awkward limitations belong in the first public release.
Somebody here must have the time to review changes, answer issues and keep the thing working. Public is a maintenance promise.
We will not publish a calendar for code that is not ready. The route matters more than the month.
The tool earns its place in real work first.
Its rough edges are known rather than merely undiscovered.
A person outside Shardly can use it without finding us first.
The repository opens after the responsibility is clear.
A public repository without documentation or maintenance is just storage with a press release.
No contribution guide for code you cannot see. No stars counter. No “community” that does not exist yet.