Instructions

@gaearon pinged me in Dec. 2015 about a tooling challenge with incentives (not listing publicly yet).

I thought it would be best for us to agree on the challenge definition & criteria to be scored against.

First, some history...
### Previous Challenge

@vjeux [initiated his challenge](http://blog.vjeux.com/2015/javascript/challenge-best-javascript-setup-for-quick-prototyping.html) with these key points:
- No setup.
- One file.
- Shareable.
- Keeps working.
- Not generic.
- Not prod-ready.

To which the community responded with (based on what I happened to :star: from the Twitter explosion)
- https://github.com/insin/nwb
- https://github.com/petehunt/rwb
- https://github.com/satya164/quik
- https://github.com/pirelenito/sagui
- https://github.com/remixz/run-js
- https://github.com/danmartinez101/react-towel

These do a pretty good job of answering @vjeux's original post. There has been a lot of progress, but limited traction in this space. From what I can gather, due to:
- Lacking publicity (e.g. link in something highly visible, such as React's documentation).
- Endorsement (e.g. famous Twitterer or Facebook).
- Scratches "hack project" itch, but largely does not transition well to a "battle-hardened, production-ready" app.
### This Challenge

If we were to challenge the community for something more impactful (to the majority of React users), although a bit of a departure from @vjeux's original post, it would require reframing the challenge in the vein of something like:

> What would need to exist to drastically change the DX for _you_ (@gaearon, @vjeux, @ericclemmons, )?
### Next Steps...

So, before writing up anymore, my question is really: **is this challenge the same as before, or do we want aim for something that'll affect the community at large**?

(My hope is that, whatever the outcome, "Getting Started" can better accommodate the various types of React users.)