docs: clarify development guide #194
Description
I guess the point I'd make is that most people aren't even going to keep this standard setup maintained and working. It's best effort, if that. So my preferred approach would be to keep this open and if someone wants to contribute an additional setup with the same maintenance model, it should be natural to do so.
In other words, based on the comments from folks above, not many people are following this guide, most just do git clone and cargo build, and I expect that to remain the same. I don't want to stop anyone from suggesting environment setups that worked for them, but I don't want to promote one of such setups to become the blessed one, discouraging all the others. There is nothing in the PR checks that would ensure these instructions stay up to date, so I don't see much value in having this blessed setup.
That said, I do think we should provide a general purpose way to run a reasonable subset of checks before publishing a PR, but I hope that can be achieved without saying you "need" this specific setup.
Originally posted by @martin-kolinek in #176 (comment)