add roadmap to README #22
Conversation
| subpackages `block`, `merkledag`, `naming`, and `routing`, which function as | ||
| laid out in the main IPFS repo_. | ||
|
|
||
| .. _repo: http://github.com/ipfs/ipfs |
There was a problem hiding this comment.
Yes, from converting from .rst to .md (because Github doesn't do checklists from .rst). Will fix it later.
There was a problem hiding this comment.
Why later?
Do you know how to amend commits and force push (not everyone does! you probably do, just checking)?
There was a problem hiding this comment.
Hi RichardLitt. "later" because I was reading on a mobile phone while on holidays. I do know how to amend and force push :)
|
Looks pretty good to me! I added some comments. |
|
Updated to address @RichardLitt's comments. |
- moved from .rst format to .md for github-native checklists
- added a roadmap inspired from js-ipfs README
- added Contribution guide also cribbed from js-ipfs
- roadmap is very much work in progress, but should help us make
a better one and split up the work.
candeira
force-pushed
the
readme-roadmap
branch
from
1dcdeed to
ccc76cf
Compare
|
Pretty complete and useful for newcomers like me, thanks! I hope to see this merged. I'm attaching a few minor corrections to typography and outdated links. README.md.diff.txt |
|
Let's just merge this. @ivilata, can you PR those diffs? |
|
Thanks, @candeira! |
|
Thanks, @RichardLitt. @diasdavid updated his own roadmap today, so we might need to revise after @ivilata's PR has gone in. Restoring the branch... |
|
@RichardLitt, I just added the changes as PR #26, thanks! |
minor corrections to typography and links after merging #22
|
Oh -- note that I think this broke |
Usage of setup.py and ``tox`` broke in ipfs-shipyard#22 when the file got renamed.
Roadmap is very much work in progress, but should help us make a better one and split up the work.