[TWiR] Call for Participation

Just, which is a make-like command runner, could use help implementing Rust-like attributes:

I am very happy to mentor and provide guidance.

A whole bunch of other features are gated on adding attributes, so this would be a much appreciated and high-impact contribution.

This would be a great first issue for something who's interested in compilers.

Hi there. I'd like to add my project, kanidm to the call for participation. This is a identity management server, akin to LDAP or AzureAD, which is fully developed in Rust. It's still in Alpha, but it has a lot of really interesting areas of development from concurrent datastructures, databases, human interaction and more. Thanks!


We're asking for people to add PowerPC64 to Rust's new asm! inline assembly macro.

We're using inline assembly for the software we are writing for our Libre-licensed PowerPC CPU/GPU, which we also are including in the call for participation.

Libre-SOC is providing €400 of funding for implementing inline assembly (via donation from NLNet).
Funding available for other tasks too.


Hello, TWiR, please help to add my project - TensorBase to "call for participation". TensorBase is building a modern bigdata warehouse in Rust, which has demonstrated its top performance even in current initial stage thanks to the Rust ecosystem and its design. Now, it is hoped to invite more interesting rusteans to join in the effort.

1 Like

I've added a help wanted label for a bunch of Ruma issues:

Issues labeled help wanted in ruma/ruma

1 Like

Hi, we have a bunch of issues with the "Help Wanted" tag on Rusty Celery:

Some more good first issues (with mentoring) in Gooseberry:

1 Like

There are some issues/new-features in diskonaut that could use help. I'd be happy to mentor for any of them:

1 Like

Let's throw a couple out there for Hacktoberfest! Nothing urgent, just things that would be nice to have.

time-rs/time#256 should not be difficult at all, just a bit tedious to do it for all fields of all types.

time-rs/time#249 should be quite easy, as it mostly involves checking for the existence of an alloc or std import.

I'm fairly certain some minor details in documentation are out of date as well, which would almost certainly be the easiest PR if you can find anything incorrect!

Drop any questions on the relevant issue. I'm more than happy to help people out!

To the people who maintain TWIR: feel free to include this throughout October so long as the issues are open.

1 Like

I'll add another for Hacktober! Also nothing that urgent; a hard-but-interesting problem that someone who's into regex might want to look into:

RustPython/RustPython#2258 - implement the _sre Python module in Rust

Feel free to keep this in for the month, as long as TWIR doesn't get overloaded with CfPs :slight_smile:

1 Like

the-way has some beginner issues:

Happy to mentor!

1 Like

Would it be possible to add this issue about heed on the next TWIR blog post, please? :slight_smile:

1 Like

Unsoundness in the time crate which can cause an unexpected segfault. User who noticed the issue notes that it may be necessary to reimplement this function entirely in Rust, rather than relying on libc. Given that I'm by no means qualified to do this (as I rarely program in C, and never with OS-level APIs), it's probably best for someone else to take this on.

1 Like

We need to get this issue going with help some help:

1 Like

Could you guys include this issue in the next blog post?

1 Like

Would love to see https://github.com/iliekturtles/uom/issues/223 included in the next TWiR.

1 Like