Steve Loeppky

There’s lots here 😅. I appreciate the feedback. It’s been heard by the team and me. I’m going to do my best to reply here. Much correspondence here comes from...

@willscott : > Anecdotally, I can say that the ipfs org is harder for my team (and I suspect non-stewards generally) to work in today than it was 18 months...

@rvagg: > go-libipfs is becoming **the kitchen-sink replacement**; it's just a shell game of kitchen sinks. We believe doing this at a library and binary level are pretty different things....

@hannahhoward : > What makes a repo in or out of `libipfs`? I think the answer that we're ending up with is: if the kubo team primarily maintains it, it's...

********************************Closing thoughts******************************** Here are some actions I believe should be taken: 1. Move relevant parts of this discussion into the go-libipfs README. I have started this [here](https://github.com/ipfs/go-libipfs/pull/171) and I have...

Give a 👍 here if you'd like to be involved a synchronous closeout this week.

Circling back to this quickly. The team has been tied up with other release and operational events this week. > Is there a realistic outcome that consists in "leaving things...

2023-02-22 update (that was also in [FIL Slack)](https://filecoinproject.slack.com/archives/C04M8232QRW/p1677109663556029?thread_ts=1677103751.480109&cid=C04M8232QRW): Kubo maintainers aren't going to do more here until we have our ducks in a row, have communicated more, and have confidence...

Reopening because there is followup work listed in https://github.com/libp2p/js-libp2p/pull/1533#pullrequestreview-1322333583 If we're tracking that somewhere else, please link and close.

@achingbrain @p-shahi : A few things on this... 1. Since there is related work underway, I adjusted the status to be "In Progress". Please fix if that is wrong or...