Shipping a Solid Rust Crate
summary
Recommend continuous integration (Travis for macOS/Linux, AppVeyor for Windows, and Joe Park’s cross for cross‑compilation) with cron nightly builds, coverage via Coveralls/Codecov, and dependency CI; pick a license (MIT/Apache‑2.0 dual is common), fill Cargo.toml metadata and badges, provide README, CONTRIBUTING, nontrivial examples, and docs that explain panics; include a code of conduct and moderation plan, announce via Herald documented.rs or forums but expect mixed reception, back any bold performance claim with data (ripgrep example), and treat empathy as the primary tool.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:38Setting Up A CI System
- 6:42Rust And The Community At Large
- 12:52Code Examples
- 13:30Code of Conduct
- 15:36Codes of Conduct You Can Use
- 18:34Make A Demo
related talks
32mBuilding and Maintaining Rust at Scale
29mPublishing High-Quality Crates
31mImproving Your Rust Life
27mThe Wonderful World of Rust Tooling
17mShipping a stable compiler every six weeks
21mRust - Cargo Cult?
48mRelease-plz: releasing crates like it's 2023
27mHow to (not) introduce Rust at your workplace - a tale