A few notes following discussion on Github, Discord, and 1:1 with Steve,

We focus on “testground as a product used by the libp2p team”, so we’re carving the shortest path between now and “the libp2p team uses testground to write test and ack every epic.”

We’re dealing with 2 non-trivial things:

• Previous maintainers have little time to contribute to the code & drive the project, so we prioritize learning.
• We don’t want to rely on the current k8s cluster (why below), and stability outside of k8s is still not clear.

In parallel with these, we expect Bloxico to improve and work on everything related to infra and running testground on K8S:

• Ability to deploy staging clusters to test new versions,
• Security of the Protocol Lab Cluster (authentication),
• Scalability of the cluster.

We would “regroup” (get rid of the temporary servers and move all our workload to their k8s work) when they are done with infra & deployment-related content, and they start working on features related to JS support, browser support, etc.

Plan

Step 1: Make Testground Work for the IP Team

Goal: have interop tests running in CI and start identifying issues.