Skip to content
This repository has been archived by the owner on Jul 1, 2022. It is now read-only.

Add links to reference implementations #8

Merged
merged 1 commit into from
Oct 24, 2016

Conversation

TimDaub
Copy link
Contributor

@TimDaub TimDaub commented Oct 20, 2016

Fixes #7

@sohkai
Copy link
Member

sohkai commented Oct 20, 2016

Not really sure it should be one of the first sections (especially before the whole read me first spiel; I was going to add it to the end sections.

@TimDaub
Copy link
Contributor Author

TimDaub commented Oct 21, 2016

Fair enough. The document itself should remain a spec.

I propose the following:

We merge this PR (as we currently have some nice traffic and I want people to see that we've started to implement), but actually we want to put the spec's content into it's own clean .md file whilst all meta data around process, organization and references goes into the document people see when they open the repository.
Kinda like here: https://github.com/ipld/specs

OK?

@sohkai
Copy link
Member

sohkai commented Oct 24, 2016

Sounds good, we can transition to the IPFS spec format once this round of edits are done (#9).

(Awkward -- it looks like my email reply last week didn't work, maybe related to the outage).

@sohkai sohkai merged commit a46ea3b into master Oct 24, 2016
@sohkai
Copy link
Member

sohkai commented Oct 25, 2016

Sounds good.

On Fri, Oct 21, 2016, 7:34 AM Tim Daubenschütz notifications@github.com
wrote:

Fair enough. The document itself should remain a spec.

I propose the following:

We merge this PR (as we currently have some nice traffic and I want people
to see that we've started to implement), but actually we want to put the
spec's content into it's own clean .md file whilst all meta data around
process, organization and references goes into the document people see when
they open the repository.
Kinda like here: https://github.com/ipld/specs

OK?


You are receiving this because you were assigned.

Reply to this email directly, view it on GitHub
#8 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AD-T8icCBgtAoUCZE77whHwKGWoQkPw8ks5q2E7JgaJpZM4KcTkh
.

@ig-shaun
Copy link

Very happy with that, thanks Tim!

Dr Shaun Conway Founding Director 9Needs - Connected Development M: +27.844099911 S: shaun.conway @9needs
On Thu, Oct 20, 2016 at 10:34 pm, Tim Daubenschütz notifications@github.com wrote:
Fair enough. The document itself should remain a spec.

I propose the following:

We merge this PR (as we currently have some nice traffic and I want people to see that we've started to implement), but actually we want to put the spec's content into it's own clean .md file whilst all meta data around process, organization and references goes into the document people see when they open the repository.
Kinda like here: https://github.com/ipld/specs [https://github.com/ipld/specs]

OK?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub [https://github.com//pull/8#issuecomment-255297582] , or mute the thread [https://github.com/notifications/unsubscribe-auth/AJfKcgr5nlZd6xTRRewfkmIelMUoGh51ks5q2E7JgaJpZM4KcTkh] .

TimDaub added a commit that referenced this pull request Jul 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants