Replies: 4 comments 1 reply
-
There's also https://discuss.libp2p.io/ |
Beta Was this translation helpful? Give feedback.
-
FYI to the future, this was a test to experience new js-libp2p discussion forum, but also curious about community support. I'm all for maintainer ease that has customer benefit. |
Beta Was this translation helpful? Give feedback.
-
There was a community call on Monday, it seems discuss.libp2p.io is going to be sunset in favour of GitHub discussions. TBH I like that it'll all be in one place going forward - I don't check discuss nearly as often as I should, but I also like that on discuss there's the opportunity for someone versed in go-libp2p to help out someone having problems with nim-libp2p (or whatever) whereas I don't see people checking the GH discussions for other projects very much. |
Beta Was this translation helpful? Give feedback.
-
I am not sure the intention of discussions should be to share cross-ecosystem knowledge because that is a very wide net and furthermore https://discuss.libp2p.io/ was still tailored to libp2p specifically. For cross implementation discussions there is still the specs repo, matrix/slack/discord and the Libp2p Community call. I have seen greater engagement in implementation specific discussions because it's all consolidated on Github, so people don't have to leave this site and so it gets checked more frequently + it's integrated with all the code and issues. All of that considered I don't see the advantages of discuss.libp2p.io |
Beta Was this translation helpful? Give feedback.
-
I'm wondering how we're going to have cross-ecosystem knowledge sharing if all the github projects in the PLN/libp2p/ipfs ecosystem all have their own isolated github repo discussions?
Beta Was this translation helpful? Give feedback.
All reactions