AnisseOli @oli closes the day with "Maintaining Rust".
"Maintenance is not just code. We are a community of contributors, not a code repository." Oli says.
After a survey among all 54 teams, Oli found that everyone is busy keeping the lights one, but no one has time to tackle the Complex problems #RustInParis
For feature work, it's "easy" to get contracted for that. Similarly, in big companies, working for months on a feature is something the company can afford. But it adds to the review load, and it might get blocked on complex refactors.
#RustInParis
#RustInParis
In rustc, Oli had that as well, with many features being blocked on a complex refactor. Another example is the infamous Rust soundness bug that needs a completely new Trait solver. The project for this Next Trait solver exists, but does not necessarily have funding. (Edit: see reply, this is incorrect).
Oli says, this is not something we can rely on volunteers for that: they'll just end up burning-out, like others before them.
#RustInParis
Oli says, this is not something we can rely on volunteers for that: they'll just end up burning-out, like others before them.
#RustInParis
After Code Maintenance, comes Community Maintenance. The project should make it easy for new contributors, and enjoyable for contributors and maintainers to contribute and review.
#RustInParis
#RustInParis
Of course, it's not always rosy: there might confilcts between contributors, or external brigading. This needs to be managed properly.
#RustInParis
#RustInParis