Porting guide

[jethrogb]

People who want to add more platforms are currently largely on their own. We
can create a guide that takes you through the steps needed to port Rust to your
preferred platform. The guide should cover everything from the initial git
clone to filing an upstream PR and beyond.

[Ericson2314]

I'd personally put this on the back-burner until the situation has improved somewhat. The current situation is too gross to be enshrined.

[IsaacWoods]

While it's a little old, I've been following this comment on Reddit by japaric, which appears to the the most complete guide. It provides little detail on the changes you'd need to make to libstd though, which is probably the most challenging bit

[antrik]

I wouldn't call it "enshrining". I believe documenting the process would help with the portability effort, by lowering entry barriers: it's hard to get more people on board with improving the situation, if it's tedious for an interested newcomer to figure out what the current situation even is...

[CarePackage17]

Such a guide would be very interesting; I'd like to see Rust on the Universal Windows Platform in the future, but while I do know that environment well enough, I don't know which parts of Rust would need changes or what today's Windows port depends on.