Reorganise and clean up the whole guide. #56
Conversation
There's almost no information in there. We can add it back when we have anything useful to say.
There was a problem hiding this comment.
this gets rid of a lot of the "broken windows", thanks :) reading the diff it does strike me that the "for reviewers" sections were acting as little summaries where you only have to read the bullet points rather than the whole section, but maybe people weren't using them? i don't feel strongly about keeping them around.
There was a problem hiding this comment.
hmm, this file seems useful - do you link something like it elsewhere?
There was a problem hiding this comment.
It's outdated and will be replaced by a new policy. See #55
generated from commit 8ef36b8
|
@rust-lang/libs This reorganises and cleans up the std-dev-guide a bit. We had a lot of nearly empty pages and a structure that made it somewhat hard to just incrementally add new information. I removed all empty stubs and not-so-useful information and tried to categorize what remained into simpler categories. ("how to contribute", "policies", "team", etc.) See https://std-dev-guide.rust-lang.org/ I'm not particularly tied to this structure/categorization; it's just what seemed to work well for the information we currently have. Feel free to move everything around if you think another structure works better. :) I might have accidentally also removed some things I miscategorized as unuseful, as I tried to err a bit on the side of cleaning up too much rather than cleaning up too little, considering the amount of incomplete and outdated info there was. ^^ |
This reorganises the guide and removes a lot of stub sections.