Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add DWeb Addressing intro and table of contents #167

Merged
1 commit merged into from
Nov 14, 2017
Merged

Add DWeb Addressing intro and table of contents #167

1 commit merged into from
Nov 14, 2017

Conversation

ghost
Copy link

@ghost ghost commented Nov 11, 2017

This is a table of contents and intro for the addressing spec. (Some of this can surely be pulled out into a blog post or so later on.)

Please take a look and give some early feedback, I have a bunch more which isn't as coherent yet. A simple LGTM is sufficient too :)

cc @diasdavid @lidel @kyledrake @Stebalien @whyrusleeping @Kubuxu @flyingzumwalt

@ghost ghost self-assigned this Nov 11, 2017
@ghost ghost added the status/in-progress In progress label Nov 11, 2017
- Network addressing
- Interoperability
- DWeb Addressing with HTTP
- URL schemes
Copy link
Member

@lidel lidel Nov 12, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would explicitly put names here ("URL schemes: ipfs:// and ipns://"), just like we have dweb: below.
It is what people usually ask about, and it makes sense to have these names pop.

@lidel
Copy link
Member

lidel commented Mar 16, 2018

@lgierth are we able to create shared branch and a PR from it so that multiple people can work on this spec document? or should I just fork the repo and create a PR from my fork?
(I tried to create dweb-addressing branch here, but I don't have permissions to this repo)

Edit: I'll just continue in https://github.com/lidel/specs/tree/dweb-addressing and create a PR against https://github.com/ipfs/specs/tree/addressing when initial draft is ready for review.

Edit 2: See ipfs-inactive/docs#91 (comment)

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants