Project name: cargo-semver-checksProject details: It's a linter that helps crates adhere to SemVer! It catches accidental breaking changes and prevents them from being published in non-major releases, which otherwise happens much more often than you'd think. Plugging it into your publish workflow is as simple as cargo semver-checks && cargo publish
Short bio: I'm Predrag 👋 I started cargo-semver-checks about 2 years ago, and I've been working on it ever since. Merging cargo-semver-checks into cargo itself is an official Rust project goal!
Looking for: Anyone who's interested in contributing new lints! Does not require any prior experience with linter tools, static analysis, compilers, etc. — just some perseverance and willingness to learn something new. Many of our lints were written by folks still attending high school or university, so if you're attending EuroRust then you're definitely qualified 😁 We could handle an arbitrary number of people, since there are many dozens of lints remaining to write.
I recommend starting by claiming a lint off of one of thesethreelists since all of those are quite easy to write. Please post in the issue that you're working on it, to avoid duplicated work! If we power through that entire list, grab any other lint marked A-lint E-mentor. Or, if you'd prefer, ping me here or in the conference chat for a suggestion tailored to your comfort level with Rust and/or cargo-semver-checks!
Project name:
cargo-semver-checksProject details: It's a linter that helps crates adhere to SemVer! It catches accidental breaking changes and prevents them from being published in non-major releases, which otherwise happens much more often than you'd think. Plugging it into your publish workflow is as simple ascargo semver-checks && cargo publishShort bio: I'm Predrag 👋 I started
cargo-semver-checksabout 2 years ago, and I've been working on it ever since. Mergingcargo-semver-checksintocargoitself is an official Rust project goal!Looking for: Anyone who's interested in contributing new lints! Does not require any prior experience with linter tools, static analysis, compilers, etc. — just some perseverance and willingness to learn something new. Many of our lints were written by folks still attending high school or university, so if you're attending EuroRust then you're definitely qualified 😁 We could handle an arbitrary number of people, since there are many dozens of lints remaining to write.
I recommend starting by claiming a lint off of one of these three lists since all of those are quite easy to write. Please post in the issue that you're working on it, to avoid duplicated work! If we power through that entire list, grab any other lint marked
A-lint E-mentor. Or, if you'd prefer, ping me here or in the conference chat for a suggestion tailored to your comfort level with Rust and/or cargo-semver-checks!If you prefer to contribute in other ways rather than writing lints, all other
E-mentorissues are fair game too!