Decentralized Beta Testing on the Internet Computer.
By Matthew Beekman and Dan Ryan
The expectations around Web3, decentralization and new innovative platforms include the ease with which a small dedicated team can leverage next generation development tools and platforms, like the Internet Computer. The result we are all looking for is an acceleration of the software development lifecycle, without sacrificing quality in our deliverables. The overhead of sysops, dev-ops and security is drastically reduced, being essentially baked into the Blockchain.
That still leaves us with acceptability testing and feedback to deal with. Most teams don’t have resources to spare, and products may risk shipping after only in-house review. We think that, in decentralized environments, the community can fill the gap.
The Internet Computer is amazing. As more developers, architects and entrepreneurs begin to understand its potential, all those here already will benefit; and that goes for our products as well. The people working today on products that might only be seen as utilities or tools are setting standards, driving innovation and clearing the way for everyone else. And we all want to ship solid, stable, innovative and helpful product.
In that vein, just recently, there was a second iteration of the Motoko Bootcamp. The event exceeded our expectations, in terms of both execution and response. The Code&State team did a brilliant job of executing, and that was reflected in the positively awesome attendance and the energy levels throughout. Thanks again to C&S for making us feel welcome. We were happy to contribute, along with a large group of developers and architects already building on the IC. We made the effort to create pre-recorded lectures, make time for adjacent live Q&A sessions during the week, and do some mentoring as well.
To all teams and builders who may have the opportunity to participate in future Motoko Bootcamp events, we can attest that it’s a no-brainer. You should dive right in. Your time contribution will feel way leveraged; the learnings are massive for students and educators alike; and it’s great fun besides. Events like Motoko Bootcamp directly drive a better community experience for everyone — and we dare say it already feels pretty terrific around here.
We want you!
To help us beta test our IC development tooling platform ICPipeline, before we launch the first version. We have tools and solutions from the beginning to production, command line tools, shared secured testing environments all bespoke to the Internet Computer ecosystem.
We’ve created a signup form right here, which should take only a couple of minutes to fill out. There is a Maybe option, if you’re unsure about committing the time.
ICPipeline is a project built for managing other people’s projects on the Internet Computer. We feel responsible to that, and we want to be extra sure the framework is solid end-to-end. We’re very close to launching the first version of ICPipeline, and we’d love to get your feedback baked into our initial release.
A demo project will be provided for all beta testers. We’re doing that to streamline the process, and it’s not to say you can’t freelance. If you think you’ll learn more about the platform by using your own build, then by all means please do — we’ll probably end up learning more that way as well.
Commencing Monday February 6th, we’ll open up the platform to all participants. After five days we’ll make another form available — as brief as we can make it — to capture your feedback and suggestions. We’ll also host an open discussion that we hope you can attend, and perhaps share some thoughts about your experience with ICPipeline.
A detailed, step-by-step task list will be provided to all testers. That, of course, will appear way more complicated than it actually is, all typed out in excruciating detail. It is ever thus. Cycles will also be provided for those who go for the optional on-chain test components, as detailed in the task list.
What are we asking you to do?
- Install the ICPipeline CLI Toolkit and run the ICPipeline Uplink daemon.
- Deploy the supplied demo project into your Local Host Replicator.
- Create a Remote Host Replicator, deploy and view the demo project in ICPipeline’s access-controlled Replicator network.
- Use your Local Host Replicator to deploy the demo project to the Internet Computer mainnet.
We tried hard to structure it so as not to take more than a couple of hours. And that can be broken up across several days. And then, of course, we’ll be interested to know what you think.
We’re suggesting specific dates, February 6–10th 2023, just to add structure, as we work hard to finalize our to-do list (you know how that goes). And we’ll be available on Discord during the five days for support as needed.
Since we know you have your own backlogs, deadlines and commitments, we’ll call that five-day timebox a guideline, not a deal-breaker. If you can knock it out by that Friday, February 10th, that will be wonderful. However, if you need more time — or if our dates don’t work for you — we’ll gladly work with you to try to find a way. If you can pitch in as your schedule allows, we’ll be no less grateful.
If it turns out that ICPipeline really adds value for you, your participation at this stage will put you on our radar. You’ll have our attention and priority support going forward. Those who follow through to the optional on-chain bits will end up with a cycles balance that’s yours to keep.
We want to emphasize that everyone in the community is welcome to participate — looking at you, Motoko Bootcampers. Your fresh perspectives are so very valuable in this context. Helping to grow the IC dev community is among our highest-order priorities, and your smoother onboarding experience is essential to that. That doesn’t just go for ICPipeline, either, but for the IC itself, the community and the ecosystem.
Anyway, thanks for reading, and we do hope you’ll consider joining ICPipeline’s pre-release beta. Here, again, is that signup link, just sayin’.
