<aside> 🪧 See the updated 202206 notice here: https://pl-strflt.notion.site/202206-Public-Notice-PL-EngRes-WG-homing-in-Filecoin-Slack-f200cf0396de4b499c095ba6d1bca1ec
</aside>
On 2022-02-12, a link to this document was posted to:
Message sent to channels:
📣 There will be more Protocol Labs presence on the IPFS Discord Server as the Protocol Labs EngRes Working Group in February 2022 is moving out of internal PL Slack to public venues. There will undoubtedly also be some channel additions/adjustments. Read more in the notice. Thanks in advance as we join in more fully 🙏.
In February 2022, the Protocol Labs EngRes WG (see link below) is moving out of internal PL Slack to public venues. For Filecoin-related conversations, they will move to the public Filecoin Slack instance. For IPFS, libp2p, and IPLD, they'll move to the IPFS Discord server, where more of the web3 developers and users that we collaborate with are. You can expect some channel additions and adjustments and more engineers from PL EngRes doing their work in the open on that server.
While Matrix was the public chat interface we publicized historically for IPFS, libp2p, and IPLD, we will focus on Discord for this transition out of internal PL Slack. The existing Matrix channels will still exist with their bridges. There are impactful issues with the Matrix/Discord bridging experience (discussed more below), but we will wait and see whether the community wants to make any adjustments.
You can learn more about the "Protocol Labs EngRes Working Group" here:
<https://pl-strflt.notion.site/PL-EngRes-Public-b5086aea86ed4f81bc7d0721c6935e1e>
(This is in a separate "Plain Text" code block because otherwise Notion converts
the link to a first-class Notion link, which requires a Notion account - arg!)
As some may be aware, Protocol Labs initiated the IPFS, libp2p, and IPLD projects and has been an active maintainer since their inception. Over the past few years, we noticed important maintainership conversations unintentionally become silo’d in the Protocol Labs Slack instance instead of open to the community - such as coordination among engineers, design discussions, technical explanations, and more.
IPFS, libp2p, and IPLD are intended to be open with many voices beyond PL EngRes stewards, and implementations beyond the reference implementations PL has spearheaded. We want to more intentionally participate in open conversations about ongoing work and improvements within these projects, share team knowledge and expertise with new protocol developers across the PL Network, and help many ongoing improvements to these protocols flourish. The convenience of PL Slack has created a barrier to that open communication. It's time to tear down that wall.