initial commit

LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2017 Juan Batiz-Benet
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

README.md

@@ -0,0 +1,12 @@
+# IPFS In Web Browsers
+> Tracking the Path to getting IPFS and other Decentralized Protocols Natively Supported in Web Browsers.
+
+## Objectives
+
+See the [ROADMAP](ROADMAP.md#the-path-to-adoption) for a breakdown of the steps we will be taking to get these protocols supported natively by web browsers.
+
+## Current Status
+
+Currently in order to run IPFS in a web browser, you have to either bundle js-ipfs with your client-side application or your users have to run a go-ipfs daemon on their local machines. This means we've completed the first step on [The Path to Native Browser Support](ROADMAP.md#the-path-to-native-browser-support).
+
+The [Sprint 13-24 February](https://github.com/ipfs/pm/issues/351) is aimed at tackling a number of the next steps.

ROADMAP.md

@@ -0,0 +1,17 @@
+Roadmap: IPFS In Web Browsers
+======
+
+_**THIS IS A WORK IN PROGRESS** We are actively working on this Roadmap. It is subject to major changes durring the current 2-week sprint. See [ipfs/in-web-browsers#23](https://github.com/ipfs/in-web-browsers/issues/23) to track the work or comment on it._
+
+**What we want:** Protocol handlers for decentralized web protocols, especially IPFS and IPLD, bundled natively in web browsers.
+
+**What we need to provide to browser manufacturers:** something that demonstrates why these protocols are valuable to their users. We have to show why distributed, decentralized protocols and technologies are valuable and we need to show specifically why IPFS is valuable.
+
+## The Path to Native Browser Support
+
+* **Step 1.** *DONE* Implement js-ipfs  
+* **Step 2.** *IN PROGRESS* Make js-ipfs and go-ipfs interoperate seamlessly (see https://github.com/ipfs/pm/issues/310, https://github.com/ipfs/pm/issues/343, https://github.com/ipfs/pm/issues/358)
+* **Step 3.** *[IN PROGRESS](https://github.com/ipfs/pm/issues/351)* Define the APIs, address schemes, security models, etc.
+* **Step 4.** *[IN PROGRESS](https://github.com/ipfs/pm/issues/351)* Create browsers add-ons and/or extensions that handle dweb protocols
+* **Step 5.** *NEXT STEP* Make the case for IPFS & Decentralized Web Protocols in Web Browsers with Use Cases, Sample Applications, Demos and [Delightful Documentation](https://github.com/ipfs/pm/issues/357)
+* **Step 6.** Native support in the Browsers: Protocol Handlers incorporated into the browsers by default