Here is some work for tokei. It should be [easy-medium] depending on the package manager and how much work is actually involved.
For someone who is interested in implementing crypto hashes or block ciphers:
Difficulty of straightforward implementation of one algorithm can vary, but i think will be around medium. Though writing optimized version can be quite hard.
There are a few “easy for newcomers” issues on diesel, e.g.:
You are very welcome to list these in TWIR and also have a look at the other open issues
Recently I started the Rust::from(lang) project in order to help transition people from other languages to Rust with articles that show how to do something in one language and then how to do it in Rust and comparing the two. Really right now what the project needs are a few things:
- Newcomers to Rust from various languages to open up issues and requests on things they’re having problems with and what languages they are familiar with.
- Seasoned Rust developers writing about either issues opened up or on topics they know how to translate from one language into Rust and the best practices to do so.
Here are some language tracking issues I’ve opened up below:
While I’m sure there are more languages this were just a few I opened. Anyone is welcome to write for whatever language or to open up an issue or request for any language.
These should be some fairly easy tasks (with steps described how to do it):
I’ll wait two weeks until I start working on the issue myself. Is that long enough? Should I wait a month?
The whole crate needs some love, but the addition of integration testing is arguably the most important, to ensure correctness. Current contributors, including myself, unfortunately don’t have a lot of free time to dedicate to the crate. There are several issues that are tagged as help-wanted.
For those interested in experimenting with tokio, there’s also this issue:
Hi! I’m helping out with crates.io now, and I’d love to help get more people contributing. I’ve got 6 E-mentor tagged issues right now that I’ve added some description to as to what’s needed to fix them. I’m going to try to keep it around that number and be responsive to questions. I’d love if some of these ended up in TWiR regularly!
I’m looking for somebody with a little experience in gnome or kde development to add a missing feature to notify-rust, a desktop notification library. The spec (on gnome at least) supports inline images in notifications though paths or by sending bitmap data directory.
I consider this medium since it requires doing a bit of research by may ultimately not involve too many lines of code . Anybody interested in improving the rust desktop integration story?
I’m looking forward to your PR resolving this issue.
I’m looking for somebody to fix a long-standing bug in the tempdir crate, and publish an improved
remove_dir_all function to crates.io in the process.
The issue is that the std remove_dir_all doesn’t work correctly on windows:
This hasn’t been fixed in-tree, where PRs get a lot of scrutiny, but it affects real code, and I open code a bad remove_dir_all myself anytime I need to remove_dir_all. In the meantime, tempdir, a popular crate with a desperate need to remove dirs, is affected by this bug.
There’s a PR open to fix tempdir:
But it is stalled. Here are my comments about what needs to happen next:
That last issue is probably the one to link from twir.
- rustup: Build with panic=abort
- rustup: Replace custom download crate with reqwest
- rustup: “update not yet available” message should not error
- rustup: Document the use of toolchain link
- rustup: Document the usage of CARGO_HOME and RUSTUP_HOME to install to a custom location
- rustup: Improve indentation of help
- rustup: Installation failure via the script has bad error message
The Ion shell project that I maintain could use some contributors to implement missing features, either in Ion or the accompanying liner project. If anyone asks, I can easily provide mentorship. I’ve done a lot of work to rewrite and complete as much of the shell’s missing features as I can, but there is still much work to be done in order to compete against existing shell languages. The codebase should be much easier to read/manage now.
Let us know links to the issues that we should post.
Rusoto, the Rust AWS SDK, is looking for maintainers. If you’re looking to learn more about Amazon Web Services, code generation in Rust or want to check out one of the bigger public code bases around (claim not validated in any manner), come check out the repository. The CONTRIBUTING file has instructions for getting started.
If documentation is more your bag, we’ve got https://rusoto.org/ which is a gitbook companion for the project. The source is on GitHub as a project under the Rusoto org on GitHub.
I’m available for mentoring.
Basically, if there is an issue that does not have an assignee, we are seeking help for implementing that feature.
I’d suggest creating a new issue looking for maintainers with information on how to contact and we’ll link to that.