Rust Community Wiki:Discussion Board
Setting up the Discussion Board[edit source]
Tracking the development status of crates[edit source]
This is a difficult problem to solve, and it can't really be fully automated. While you can get somewhere by developing some heuristics, they will inevitably leave something to be desired. If we assume that we use the following things for our heuristic, then I can think of a few shortcomings:
- The "maintenance" badge.
- The date of the last version published to crates.io.
- The date of the last commit in the main repository.
- The frequency of commits in the main repository.
- The "maintenance" badge could be stuck at "actively-developed" or "passively-maintained" in spite of its real status if the author(s) abandon the crate without updating the status.
- "Date of last version published to crates.io" is only somewhat useful for telling whether the crate is dead or not.
- Tracking commits to the main repository will miss development that is happening elsewhere.
pijulis one example of this, where the author has decided to develop the crate in private for some time before publishing the changes.
In addition to the above issues, there's also the fact that the development status of crates will change over time. It seems a bit unreasonable to expect that every ecosystem overview stays up-to-date without some sort of system or process behind it.
To alleviate this, I propose that a bot is written which will:
- Track crates.io releases
- Track commit frequency and dates
- Look at the maintenance badge
Based on this, it will update both its own user page with information on which pages and crates might need checking. It might also pull from a pool of volunteers and assign some number of crates and pages to some number of volunteers. In addition to the main heuristic(s), the bot should also assign pages and crates for a check-up at some regular interval.
Resolved Discussions[edit source]
Licensing of the Rust logo[edit source]
The Rust logo is licensed under the terms of the Creative Commons Attribution license (CC-BY).