Epic: Create Roadmap to Being Native in Web Browsers

[flyingzumwalt]

Complete the ROADMAP.md

• Fill out all the steps
• Situate within the broader effort to upgrade the web - see "Browser Upgrade Path" in these slides
• Validate the plan with people who know how browser teams work

[flyingzumwalt]

@nicola here are the notes from our conversation. https://github.com/ipfs/in-web-browsers/blob/feat/roadmap/roadmap-stages-of-integration.md It's a mess right now -- our notes barely captured half of what we discussed 😞

[flyingzumwalt]

I'm struggling around security models and their impact on this roadmap -- there's no way to define a clear roadmap until you establish some semblance of a framework for the relevant security concerns. Writing a protocol handler that runs ipfs and exposes the ipfs core interface (see #39 and its sub-issues) is not the hard part. The real challenge is to expose that functionality in a way that is safe. See #43 (huge topic).

Without a framework for thinking about these security models, it's hard to sort out what the roadmap should look like. What are the stages of adoption/integration? It's clear that there are certain stopping points where you can provide XYZ functionality without creating vulerability A, but can't safely allow some other functionality until you address that vulnerability...

[SgtPooki]

@lidel @BigLep Is this something we need to keep updated? Who owns this?