ShardlyHQ

Front page

Open source

The honest version: not much is open yet.

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.

Current state
Mostly closed source
01Right now

Nothing padded out for appearances.

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.

Today

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.

Closed

Most product work

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.

02The release standard

If it goes public, it stays ours to support.

Opening code is the start of a job, not the end of an announcement. Three things have to be true before we do it.

Useful outside this building

We will publish tools that solve a real problem on their own, not scraps separated from the part that made them useful.

Documented before announced

A README is the floor. Installation, examples and the awkward limitations belong in the first public release.

Owned after release

Somebody here must have the time to review changes, answer issues and keep the thing working. Public is a maintenance promise.

03How work gets out

No date. A sequence.

We will not publish a calendar for code that is not ready. The route matters more than the month.

  1. 01Used internally

    The tool earns its place in real work first.

  2. 02Stable enough

    Its rough edges are known rather than merely undiscovered.

  3. 03Explained properly

    A person outside Shardly can use it without finding us first.

  4. 04Published and maintained

    The repository opens after the responsibility is clear.

A public repository without documentation or maintenance is just storage with a press release.
Watch this space, quietly

When there is more, it will be here.

No contribution guide for code you cannot see. No stars counter. No “community” that does not exist yet.