A great place for people to contribute a little or lot for hyper, a meta task with many easy small tasks listed out:
Hi all ,
Some issues available for r
- [tuify] Use nice ANSI symbols instead of ">" to decorate what row is currently selected · Issue #133 · r3bl-org/r3bl_rs_utils · GitHub
- [all] Use nu shell scripts (not just or fish) and add Github Actions to build & test on mac & linux · Issue #120 · r3bl-org/r3bl_rs_utils · GitHub
- [tuify] Use offscreen buffer from r3bl_tui to make repaints smooth · Issue #118 · r3bl-org/r3bl_rs_utils · GitHub
Hi there We have good first issues at Ockam that we could use your help with:
Some issues available for DeepCausality. DeepCausality is a hyper-geometric computational causality library. While this crate may look daunting at first, we have some easy beginner friendly tasks open:
Thank you .
If people are interested in contributing to a networking library or want to get an insight into a larger Rust workspace, we'd have some easier issues to tackle over at
- replace `custom-clippy` alias with workspace-wide `[lints]` configuration · Issue #4484 · libp2p/rust-libp2p · GitHub
- Prefer tokio runtime everywhere · Issue #4449 · libp2p/rust-libp2p · GitHub
- misc: make `RwStreamSink` an implementation detail of the memory transport · Issue #4345 · libp2p/rust-libp2p · GitHub
Here are a few documentation items for the
- Missing panic condition on API docs · Issue #623 · time-rs/time · GitHub
This would amount to going through, finding where there are intentional panics, and documenting them. This is more tedious than anything.
- Add comparison to chrono to the docs · Issue #308 · time-rs/time · GitHub
I have not used
chronoin 4ish years at this point. I am not familiar with its intricacies and as such am unable to create a comparison beyond the immediately obvious. If someone has knowledge of both
time, this would be a good issue.
- The Book is hardly readable · Issue #327 · time-rs/time · GitHub
Definitely the biggest of the three. The sections in the sidebar can be cut down significantly, as most of them likely won't be much more than what's already present in the crate's documentation. But having a basic introduction to the crate seems reasonable imo.
Documentation isn't my strong suit, so having others provide the basics would be super useful!
Hey, we have a lot of issues for community contributors, here are some of them:
Here are some more issues of varying difficulty that are well-suited for external contributors: