-
Notifications
You must be signed in to change notification settings - Fork 48
Create Rust IPFS Blog Post #384
Create Rust IPFS Blog Post #384
Conversation
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3 more changes, but after that LGTM
As you can see in the [Rust-IPFS DevGrant Roadmap](https://github.com/ipfs/devgrants/tree/master/open-grants/ipfs-rust) implementation work | ||
takes place mostly over early Q2 2020 and covers the use case of **IPLD applications**, | ||
targeting the low-level blockstore, libp2p integration, and IPLD-related functionality | ||
such as `ipfs dag put` and `ipfs dag get`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: add in an image of the three phases of the roadmap at a high level?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's a great idea, though I'm not personally a graphic designer...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
such as `ipfs dag put` and `ipfs dag get`. | |
such as `ipfs dag put` and `ipfs dag get`. | |
![Rust IPFS Timeline](https://gateway.ipfs.io/ipfs/QmU7sssvo52Rrwj7MWZNpeHnFjjdG271Dx5zfGkZSbgVnN) |
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me the most important thing for this blog post was to make clear where the entry point for interested people is, and that is clear. I originally thought I would want to go into more detail about that, but the current blog post captures it well. In case there's any confusion about the lower level libs (e.g. Multiformats) we can always do another blog post.
Added the presumptive URL for the Equilibrium post. I believe this is ready for merge! |
@@ -0,0 +1,60 @@ | |||
--- | |||
date: 2020-03-16 | |||
url: 2020-03-16-announcing-rust-ipfs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
url: 2020-03-16-announcing-rust-ipfs | |
url: 2020-03-18-announcing-rust-ipfs |
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
@momack2 All set! |
Submitting a rough draft of the Rust IPFS blog post. I put an index of 085 on it and a date of March 16 to post. What I'd like to do, pending approval here, is afterward write the longer, more technical and in-depth post on the Equilibrium Blog. We can launch them together and cross-link.
@vmx and whomever else are welcome to share the byline there as well.
cc @momack2 for review