<aside> ☠️ This document was last updated in December 2022. It is currently out-of-date due to changes made to the team set up. For H2 2023 roadmap, see https://github.com/pl-strflt/ipdx/issues/81.

</aside>

<aside> ⚠️ This document describes the general IPDX roadmap for 2023. It does NOT cover the Testground project roadmap which is was our top priority. It references it but for a full breakdown you should see GitHub instead.

</aside>

<aside> 💁 If you’re interested in a high-level overview, you can head directly to the ✈️ High-level milestones section.

</aside>

Foreword

IPDX (InterPlanetary Developer Experience) is uniquely positioned to work across the ecosystem to improve the developer experience. We should have enough visibility to provide general solutions to common problems. We have to be quick at noticing impoverished experience and fix it before it becomes a pattern. We have to be pioneers in the current best DX practices and be proactive at promoting them among the developer community.

To be able to successfully deliver on the above, we require sufficient time for exploration efforts — Exploration of both new technologies and developer needs. To allow that, we have to be very precise and clever about the impact areas we want to focus on. We also need to ramp up our hiring efforts.

We align ourselves with the Testground roadmap to multiply our team’s impact. We believe that by solving Testground DX issues, we can both advance the Testground project and develop solutions that apply in other projects.

This document is designed to guide the team throughout 2023, but it should not be treated as final. We should feel empowered to update it as we learn new information, gain new team members, etc.

Any feedback on how we intend to work is highly encouraged! Feel free to drop us a comment here or reach us on Slack in the #ipdx channel.

Customers

In this section, we identify our main customers for 2023. This helps us be precise in our prioritizations and scheduling.

1. 🧑‍🔬 Testground Contributors

The 2022 Testground revival efforts brought the project to a stage where it is actively used — both internally by the libp2p team, as well as externally. As such, it became our biggest project in terms of user base.

We believe that by focusing on improving the Testground contributor experience through generally applicable solutions, we’ll be able to not only positively impact Testground development velocity and adoption, but also improve the developer experience in our other interest areas. We want to treat Testground contributors as our first customers who get to beta-test our solutions.

By focusing on a project we own, we’ll be able to keep the feedback loop tight. It’ll allow us to build the right thing for at least one concrete group of developers. Finally, it’ll help us battle our current staffing shortcomings. We’ll be able to advance general DX standing, while pushing the Testground project forward.

Needs