Suggest A Project
The future catalog can help maintainers show what their tools and databases do in a reproducible, properly credited lab. Open-source suggestions are welcome. Commercial and private projects are possible too, but they need a different conversation before any integration is planned.
Get in touch
Section titled “Get in touch”- Send Kay Sauter a LinkedIn message.
- Use the Kay On Data contact form.
- For a public, open-source proposal, a GitHub issue is also an option.
Commercial project owners must contact Kay first so licensing, distribution, product positioning, support expectations, and any demonstration agreement can be discussed. Do not open a public issue containing confidential commercial details.
Private or internal projects can be used through a local path or protected source when the access model, secret handling, provenance, permitted actions, and cleanup obligations are understood. Credentials must never be placed in a URL or public issue.
What to include
Section titled “What to include”Please provide:
- the project or dataset name, official home, owner, and maintainer contacts;
- the license, usage terms, attribution, and redistribution rules;
- supported platforms, versions, targets, and required privileges;
- a pinned release, digest, or other immutable acquisition source;
- any published checksum, signature, or software-bill-of-materials information;
- installation, restore, import, verification, and removal steps;
- the lab scenario and learning outcome;
- expected network access, cost, and external services;
- whether the artifact or data can contain personal, confidential, or regulated information.
A public catalog entry requires known license or usage terms. Automated downloads also need a reproducible version and must verify a checksum or signature when upstream provides one.
What inclusion means
Section titled “What inclusion means”A suggestion is not an integration promise. It must pass architecture, security, licensing, provenance, maintenance, testability, and cost review before automation is considered.
If accepted later, the catalog will keep upstream ownership visible, link to authoritative sources, record exactly what is downloaded or executed, and explain how the artifact is verified and removed.