Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Retire kubo-as-a-library #10175

Open
6 tasks
hacdias opened this issue Oct 9, 2023 · 0 comments
Open
6 tasks

Retire kubo-as-a-library #10175

hacdias opened this issue Oct 9, 2023 · 0 comments
Labels
effort/days Estimated to take multiple days, but less than a week P2 Medium: Good to have, but can wait until someone steps up

Comments

@hacdias
Copy link
Member

hacdias commented Oct 9, 2023 •
edited
Loading

This is the tracking issue to "get rid" of kubo-as-alibrary. In the long run, we do not want Kubo to be used as a library. Kubo is an IPFS implementation, while the core library parts are living in Boxo.

Tasks
Beta Give feedback
@hacdias hacdias moved this to 🥞 Todo in IPFS Shipyard Team Oct 9, 2023
@BigLep BigLep mentioned this issue Nov 9, 2023
Closed
11 tasks
@hacdias hacdias added P1 High: Likely tackled by core team if no one steps up P2 Medium: Good to have, but can wait until someone steps up effort/days Estimated to take multiple days, but less than a week and removed P1 High: Likely tackled by core team if no one steps up labels Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/days Estimated to take multiple days, but less than a week P2 Medium: Good to have, but can wait until someone steps up
Projects
No open projects
IPFS Shipyard Team
Status: 🥞 Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hacdias