I feel some kind of Developers' Guide is useful. Location is less important than ensuring it is easy to find.

It should include information on how to find previous discussion on an issue. One doesn't want to spend time on something that the wider community has either rejected or deferred for reasons that may not be obvious to the newcomer.

A style guide is important in keeping the look of the code consistent. I will submit that once such is in place, the existing code will need to be reviewed to provide a good example for comparison.

I think the links to the earlier items as above are good and should be encouraged.

I agree, this would be useful to as a place to collect and post this information, that is currently mostly scattered throughout closed and open issues.

I think the Wiki is a good place to put this.

We can start by adding Richard's comment, and the other issues you've linked.

I put some (very minimal) information on the wiki to get this project started: https://github.com/gopherjs/gopherjs/wiki/Developer-Guidelines

If we're happy with this, we can probably close this issue, and just start keeping that page up to date.

That looks like a great start, thanks for doing it!

If we're happy with this, we can probably close this issue, and just start keeping that page up to date.

Let's do that. It'll help keep the open issue count lower, down to just actionable ones.

I think that page looks great and it's useful. Thanks again for doing this!