I'd like to suggest that it might be worth while to begin formulating a sort of Developers' Guidelines document somewhere, which documents official and semi-official guidelines, preferences, and expectations of new developers contributing to GopherJS directly, and perhaps those writing modules for use by the GopherJS community.

As a recent sample of two items that might fit in such a document:

• Stance on ECMAScript 6
• Always document exported functions, and otherwise follow Go upstream standards

Also (added by @shurcooL):

• Proposal: Move towards a more flexible, low level compiler testing system like that of Go.

I realize there are likely very few "official" decisions to document right now, but I expect that will change (and is changing!).

Currently, we have just the issue tracker, but something more digested for newcomers I think would be appropriate.

Would this be welcomed? And if so, where should it live? Some obvious (to me) options:

• DEVELOPERS.md in the main repo
  • On the wiki
  • The gopherjs-book repo (??)