Agreed. Why overcomplicate things? I can understand the desire not to pick favourites in a rapidly-evolving space which was clearly the approach of /r/rust mods early on, but enough time has now passed that the project could save everyone some headaches by just picking one Lemmy community that they’re confident will be held to the Rust community standards. Nobody’s expecting a permanent decision with young software. We can change the way we operate again in a year or two if we have to.

Previous years:

• 2021
• 2020
• 2019

I continue to be a little disappointed how brief these have become since 2019, given how exhaustive the questions are.

One approach I’m personally fond of is actor-style async programming with tokio. It’s easy to mingle timers with receiving messages from channels, which is quite powerful. This post by Alice Rhyl is a good description of the idea: https://ryhl.io/blog/actors-with-tokio/

Yes. The interaction with the Rust Foundation is described in the linked RFC.

The Council is responsible for establishing the process for selecting Project directors. The Project directors are the mechanism by which the Rust Project’s interests are reflected on the Rust Foundation board.

The Council delegates a purview to the Project directors to represent the Project’s interests on the Foundation Board and to make certain decisions on Foundation-related matters. The exact boundaries of that purview are out of scope for this RFC.

I suspect parent was talking about the number of subscribers to the Rust community on each server (currently 174 on P.D, 591 on lemmyrs). Which server people choose as the “home base” for their account so to speak is an interesting reflection of that server’s maturity/impact but not the major driver of community activity.