-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Coalescing the go-ipfs project repos #6862
Comments
Note: this isn't happening till 0.5.0 is out. |
libp2p has started libp2p/go-libp2p#829 |
I wouldn't mind some (or all) of the go-ipld repos across to the ipld org. In particular I'm working on some btc, zcash and eth stuff at the moment and would like to work on those libraries. We already have js-ipld-* versions in the ipld org so the Go ones may as well move too unless someone's particularly attached to them here. |
@rvagg ack, will do. |
We had a convo and are probably going to merge go-block-format into go-ipld-format (not immediately, but soon). |
Please be careful. Moving libraries in go is not trivial because import paths need to be updated. See what I did for https://github.com/ipfs/go-car/. |
Correct, will move and alias to avoid breakage. |
Something we forgot: We need to:
|
Is the gateway extraction something @thattommyhall could implement? Is this migration work active or on-hold for now? |
The gateway extraction should be simple, I think. |
This has essentially more or less happend with the |
Did not meant to close, there is stuff inside Kubo that could be worth moving. |
Back in Jan 13, me, @Stebalien and @hsanjuan sat down and discussed a potential endeavor to decrease the repo surface area of go-ipfs. The result was a lit of repos and action items for each (merge into another repo, move to another org and/or deprecated)
The list is here:
Next steps is for @hsanjuan to take a new look at this list from the eyes of the new developer experience special interest group.
The text was updated successfully, but these errors were encountered: