“Slimmer Kubo”: Trim out unnecessary code
reidlw opened this issue · comments
eta:2023-03-31
description:
Clean up old, non-critical functionality from Kubo to limit supported surface area and help team focus on strategic priorities/functionality.
Kubo today has become a bit bloated with functionality that is not critical to our key use cases, has not been touched in a long time, etc. We then get issues opened against that functionality or questions about it, which diverts team time/resources away from key strategic work. We would like to clean some of this out of Kubo to help us be more efficient/effective, and focused on top priorities.
Done:
Remove some specific things: Fuse, graphsync, others based on analysis
This actually requires a multi-part deprecation strategy, so we would start with deprecation, with code removal occurring potentially 6 months later.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.