How to contribute
The samples are written and verified by CodeSampleX. Everything around them is open, and the part that actually needs other people is open first.
Every official CodeSampleX sample is generated independently and verified by running its contract. The project does not accept sample code whose origin it cannot establish.
Open to anyone, no account
-
Usage evidence
csx reports which public package and version you used, whether the build or test passed, and a sanitized failure fingerprint when it did not. Source code, file paths, project names, secrets and raw logs never leave the machine — in local-only mode nothing leaves it at all. This needs no account and no identity.
-
Verification on your machine
This is the one thing the project cannot do alone. A sample is verified on the machines that exist, and yours has a libc version, a runtime build and an OS that no amount of work here can substitute for. A second machine agreeing is what moves a sample from PUBLISHED to CROSS_PASS; the ladder is built out of other people's computers.
-
Bugs and patch notes
The most valuable report is a release note: a library fixed something, and nobody wrote down what actually changed. That becomes a regression case — the old version fails the contract, the new one passes it — and the pair is worth more than either half. Report the library, the versions, and what you saw.
-
Asking for a sample
There is no form, because the asking is already counted. Every search that ends in NO_SAFE_MATCH is recorded as a request for that package, so using csx and getting no answer is itself the request. The board is public and it is the project's to-do list.
Why sample code is not accepted
A sample is worth exactly what its origin is worth. Code of unknown provenance brings a licence nobody can trace, a real chance that it belongs to somebody's employer, and no way to check where it was copied from — and unlike a wrong answer, none of that can be taken back once other people's agents have read it. The rule this project applies to search applies to contribution too: a wrong sample is worse than a missing one.
This may open later, and if it does it will open as a proposal rather than a donation: the package, the API, the use case and a link to the documentation — with the code still generated in a clean room and verified here.