Continuing the discussion from Let's talk about ecosystem documentation
I have this suggestion there are times when a code base of a “thing” is not update anymore (like the lear developer lost interest or can’t continue working), or times when the documentation is little outdated even that the code is fine.
When a lead developer lost interest, it also will not point to the useful forks if there are any one, you will have look if you search and find the actual current fork.
So I suggest this, crates take from github code, why not make a
rust-community organization, and start transferring repos there (yeah it will take time), then developers could give/request access, and if the original autor lost interest, doesnt want to update the docs and so on the persons in the organization could make it work again, or update it, or transfer to another organization like
rust-community-deprecated (don’t know).
But I will also suggest a
Anyway, there are “organizations”, I think they could help in centralize things without the original developers losing own right of each crate.
If not for crates, at less for “tutorials”.