ipfs-shipyard / ipfs-shipyard/py-ipfs

passing a common test suite (which we'll extract from go-ipfs)

Open
#17 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
476
Forks
90
PR merge metrics
No merged PRs in 30d

Description

@jbenet calls this out in #1. Judging by #8 people seem to agree with the principle that developing against a testable spec is a priority.

I'm curious how we're going to go about accomplishing and structuring this goal. I realize the actual written spec is still in progress (I myself am still coming up to speed on the protocol specifics).

I'd like to use this issue to center discussion on planning for how we're going to tackle this issue.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.