Add new, smaller next milestone: Developer Invite-Only Beta

[danfinlay]

A few of the larger tasks on the current milestone involve fixing our RPC backend architecture, and making it more robust.

Considering many devs are already running their own RPC nodes, or test-RPCs, I don't think it's asking too much that they provide their own RPCs.

If we say the next milestone is to provide a minimal set of features to allow devs to experience Metamask and prepare their Dapps for compatability, we can put off those backend tasks to a later milestone, and deliver some value to our developer community sooner.

[danfinlay]

Big bonus points if we can identify a milestone small enough that it's ready for the sxsw music-blockchains hackathon next week.

[danfinlay]

I just reviewed it, and Account CRUD seems like the most necessary, and even it seems kindof optional. If we can get the genesis.json config on testrpc, plus some documentation, it might be good enough for a private developer launch, and sharing at sxsw.

[kumavis]

i think adding a new milestone is well defined and makes sense, but who are we distributing the plugin to?

[danfinlay]

If people are hosting their own RPCs for this hypothetical release, what’s keeping us from making it a “developer preview”, just publicized only to devs?

On Mar 8, 2016, at 5:09 PM, kumavis notifications@github.com wrote:

i think adding a new milestone is well defined and makes sense, but who are we distributing the plugin to?

—
Reply to this email directly or view it on GitHub #42 (comment).

[danfinlay]

Added as sxsw hackathon