MyZubster: reorganizing an open-source ecosystem for robots, IoT, drones and quantum technologies
MyZubster is growing, and with growth comes a problem every open-source project eventually faces: organization.
We recently reorganized the issue structure of the MyZubster ecosystem to make contributions easier to understand, track and complete.
The goal is simple:
Every issue should belong to a clear project, milestone and contribution path.
🧩 From one milestone to a structured roadmap
Previously, a large number of issues had ended up grouped under the same milestone.
That made it harder to understand what belonged to which project.
We have now reorganized the repository into dedicated milestones:
Milestone Project Issues
2 EVA IONI #1–#8
3 Urban Lab Drone #9–#11
4 Orto Urbano IoT #12–#13
5 Quantum Wallet #14–#15
6 3D Reconstruction #17–#22
7 Documentation & Community #16, #23
This gives us a much clearer roadmap for contributors.
🤖 EVA IONI
The first group focuses on EVA IONI, our robotics and automation direction.
The issues cover the different components needed to develop the project and connect robotics with the wider MyZubster ecosystem.
The objective isn't simply to build a robot.
It's to create an open platform where hardware, software, automation and community contributions can work together.
🚁 Urban Lab Drone
Issues #9–#11 are dedicated to the Urban Lab Drone.
This area explores autonomous aerial systems, mapping and the collection of environmental data.
The long-term vision is to connect drone data with other components of the ecosystem, including robotics, urban agriculture and 3D mapping.
🌱 Urban IoT Garden
Issues #12–#13 cover the Orto Urbano IoT project.
The idea is to combine sensors, automation and open-source software to monitor and manage urban growing environments.
This creates an interesting bridge between:
IoT
robotics
environmental monitoring
automation
open hardware
⚛️ Quantum Wallet
Issues #14–#15 belong to the Quantum Wallet milestone.
This part of the project explores cryptography, wallets and technologies that could become relevant as quantum computing evolves.
The important part here is experimentation and research rather than pretending that every component is already production-ready.
🧊 3D Reconstruction
Issues #17–#22 remain under 3D Reconstruction.
This work is particularly interesting for robotics and autonomous systems.
A robot or drone that can understand its environment needs more than raw sensor data: it needs a representation of the world it is operating in.
3D reconstruction can therefore become a common layer connecting:
drone → sensors → mapping → robotics → environment
📚 Documentation & Community
Finally, issues #16 and #23 are dedicated to documentation and community.
This may sound less exciting than robotics or drones, but it is actually one of the most important parts of an open-source ecosystem.
If nobody can understand how a project works, it cannot scale.
Good documentation is infrastructure.
Why this reorganization matters
The biggest improvement isn't the number of milestones.
It's traceability.
A contributor should be able to go from:
Project → Milestone → Issue → Pull Request → Merge
without having to guess where their work belongs.
This also makes it easier to evaluate contributions and eventually connect completed work with the project's bounty system.
💰 Contributions and bounties
MyZubster uses GitHub issues as the primary starting point for contributions.
A contributor can select an issue, work on it, submit a Pull Request and have the contribution reviewed.
The intended workflow is:
Issue
↓
Contributor
↓
Implementation
↓
Pull Request
↓
Review
↓
Merge
↓
Bounty verification
↓
Payment
This structure allows us to keep technical work and contribution accounting connected.
Of course, a bounty is only considered payable after the relevant contribution has been properly verified and merged according to the project's rules.
Open source is also an experiment in coordination
One of the interesting things about building MyZubster is that the technical architecture isn't the only architecture we need to design.
We also need an architecture for collaboration.
Repositories, issues, labels, milestones, pull requests, documentation and contributors are all part of that system.
That's why we're treating GitHub not just as a place to store code, but as part of the project's operational infrastructure.
What's next?
With the milestones reorganized, the next step is to work through the issues systematically.
The priorities are:
improve documentation;
validate existing issues;
connect issues with concrete implementation tasks;
review incoming pull requests;
verify contributors and completed work;
merge validated contributions;
process eligible bounties.
The objective is to make MyZubster increasingly transparent, reproducible and contributor-friendly.
If you're interested in robotics, drones, IoT, urban agriculture, cryptography, 3D reconstruction or open-source infrastructure, there are several areas where you can participate.
🚀 Join the project
You can explore the repositories and issues here:
MyZubster-Ecosystem on GitHub
The documentation repository:
MyZubster Manuals
And the project website:
MyZubster
Build with us. Document with us. Break things, fix them, and contribute.
