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.

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

[Milestone] Getting boxo "over the hump" #196

Closed
24 of 26 tasks
BigLep opened this issue Mar 7, 2023 · 7 comments
Closed
24 of 26 tasks

[Milestone] Getting boxo "over the hump" #196

BigLep opened this issue Mar 7, 2023 · 7 comments
Assignees
Labels
topic/project-management Items related to organizing and managing this project well.

Comments

@BigLep
Copy link
Contributor

BigLep commented Mar 7, 2023

Background

boxo has been in limbo state for a couple of months which doesn't maximize its utility for maintainers and potential consumers and it doesn't instill confidence in existing consumers who are impacted.

This is a tracking issue for the work for getting boxo to a place of providing value for its intended audience and being clear for those involved and affected on what they can expect going forward.

Done Criteria

The Tasks below are completed. This includes both the various communication pieces and the resulting release in #202.

Phases

🪧 The "Staging/validation phase" and "Documentation/community-focus phase" can happen in parallel. They must complete before the "Disruption phase".

How can I follow along progress?

Major updates will be posted here. The tracking of copying in specific repos will occur in #202 .

Related Items

There are other topic/project-management that are being created as part of this endeavor but aren't blockers for meeting the done criteria.

@BigLep BigLep added the topic/project-management Items related to organizing and managing this project well. label Mar 7, 2023
@BigLep BigLep moved this to 🥞 Todo in IPFS Shipyard Team Mar 10, 2023
@BigLep BigLep moved this from 🥞 Todo to 🏃‍♀️ In Progress in IPFS Shipyard Team Mar 10, 2023
@BigLep
Copy link
Contributor Author

BigLep commented Mar 10, 2023

2023-03-09 update:

  1. Plans to copy repos into go-libipfs with deprecated types rather than fully migrate them over is being planned per [Design/discussion/decision] Whether to "migrate" or "copy" repos into go-libipfs #191 (comment)
  2. This issue's description has been more fully flushed out with the specific tasks.
  3. There will be a lot more activity on this endeavor the week of 2023-03-13 given @ipfs/kubo-maintainers are close to completing Release 0.19 kubo#9502

@BigLep BigLep closed this as completed Mar 10, 2023
@github-project-automation github-project-automation bot moved this from 🏃‍♀️ In Progress to 🎉 Done in IPFS Shipyard Team Mar 10, 2023
@BigLep BigLep reopened this Mar 10, 2023
@BigLep BigLep moved this from 🎉 Done to 🏃‍♀️ In Progress in IPFS Shipyard Team Mar 10, 2023
@BigLep
Copy link
Contributor Author

BigLep commented Mar 10, 2023

2023-03-10 update: further broke out the tasks in the issue description. A key tenant is that we don't start adding "not maintained" README notices and deprecated types in repos until all the documentation items in go-libipfs are handled. When we start signposting more people to go-libipfs, they should get a strong sense that go-libipfs is thought-through and well-maintained (i.e., treated like someone's baby).

@BigLep
Copy link
Contributor Author

BigLep commented Mar 29, 2023

2023-03-29 high level update:

@BigLep BigLep mentioned this issue Apr 5, 2023
3 tasks
@BigLep
Copy link
Contributor Author

BigLep commented Apr 6, 2023

2023-04-06 update: Boxo 0.8.0 was released which has the copied repos included (#264 ). We're continuing to update the tracker above as progress is made.

@BigLep
Copy link
Contributor Author

BigLep commented Apr 12, 2023

2023-04-12 update:
Deprecated types and "not maintained" statuses will not be added until the week of 2023-04-24 (after IPFS Thing).

Various docs about this effort have been created or updated:

  1. https://github.com/ipfs/boxo/blob/main/README.md
  2. https://github.com/ipfs/boxo/blob/main/RELEASE.md
  3. https://github.com/ipfs/boxo/wiki/Rationale-of-2023Q1-Repo-Consolidation-Effort
  4. https://github.com/ipfs/boxo/wiki/Copied-or-Migrated-Repos-FAQ

@BigLep
Copy link
Contributor Author

BigLep commented May 26, 2023

Update on where we're at based on 2023-05-25 maintainer conversation:

First off, fully finishing this off isn't done yet. The progress this week was to get the readme notices of "not maintained" added to the various repos.

To finish this we need to handle go-car and get Lotus fully migrated to Boxo.

Unfortunately that work is blocked by universes colliding due to global variables. This will get addressed in #291

That is the top next priority as soon as @aschmahmann or @Jorropo finish their other inflight work on the board.

@BigLep
Copy link
Contributor Author

BigLep commented Jun 30, 2023

Everything is done here except for #203 . That still needs to be done, but will get picked up in Q3. From end user regard, the goals of this issue have been addressed and as a result, I'm going to close it.
Thanks to all involved in making this happen. (Easter egg that PR with readme logo was pushed today: #405)

@BigLep BigLep closed this as completed Jun 30, 2023
@github-project-automation github-project-automation bot moved this from 🏃‍♀️ In Progress to 🎉 Done in IPFS Shipyard Team Jun 30, 2023
@hacdias hacdias unpinned this issue Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic/project-management Items related to organizing and managing this project well.
Projects
No open projects
Archived in project
Development

No branches or pull requests

3 participants