-
The work continues!
The work on OctoMY™ never really stops. If you want to join the effort and create the new history, please see how to contribute!
-
Website reboot
We put Google Sites Classic behind us and created the website the project deserved based on Python + FastAPI + jinja2 + Bootstrap. 🥳
-
Migrate to Qbs
The project migrated from qmake build system to Qbs
-
Migrate to Qt6
The project migrated from Qt5 to Qt6. Arguably it is Qter than ever😅
-
Hiatus
The project took a well deserved break to properly saviour COVID19😷🤕🤒 and other disasters💣🪖💥⚔️😢 properly. But in the darkeness the monster did not sleep...
-
Migration to gitlab
The project was migrated from github to gitlab.
-
Makeover completed
The project overhaul (a.k.a. OctoMY™ v2) was completed successfully after intense efforts for 6 months and the project was now becomming very mature.
Some highlights:
- No compiler warnings or errors allowed.
- Some libraries renamed to better more descriptive names.
- Some libraries merged.
- Some libraries split up, especially libcore and libutil.
- Some libraries or parts will be removed outright.
- Widgets and ui files are distributed among the libraries they belong to.
- Resource files are distributed among the libraries they belong to.
- All libraries receive README.md to describe them better.
- Formatting of sources modified to follow the standard.
- Translation unit optimizations to reduce buildtime.
-
Third Anniversary
The project celebrated it's 3rd anniversary and a plan to completely overhaul the project was unveiled (a.k.a. OctoMY™ v2)
-
License Update
The mandate and license was updated.
-
Second Anniversary
The project celebrated 2nd year anniversary.
-
Mandate unveiled
The official OctoMY™ mandate was created and subsequently all the communication was changed to align with the goals of the mandate.
-
First Anniversary
The project celebrated it's 1st year anniversary🥳.
By the end of it's first year, the OctoMY™ project had come surprisingly far:
- The project compiled to Desktop and Android targets.
- The project had an alright security model in its core.
- Lot's of time had gone into making it user-friendly for the beginner while not getting in the way of the experts, and it showed.
- The project was running very stable thanks to quality being thought of from the start. It had already started racking up quite a lot of automated tests.
- It incorporated a protocol for discovery, pairing and communication with peers over UDP.
- It incorporated a gait planner for legged robots.
- It incorporated facial expressions, speech, stats logging and a HUD.
- It was still very much work in progress, and features would break every day. It was still not ready for the masses, but very close.
-
Blog started
The OctoMY™ blog was started! It was actually converted from Lennart's old personal blog, but since that blog had already started talking 90% about the OctoMY™ project, a name and brand change was in order.
-
Project founded
The OctoMY™ project was officially started, after the founder bought one of these:
for X-Mas.
After we had a great time assembling it he was shocked at the poor state of the software that came with the kit. It barely managed to play back some pre-recorded animations, and definitely none of the fancy Phoenix stuff that we anticipated after watching a whole lot of videos on YouTube.
So as an experienced developer and hobby robot enthusiast Lennart set out to "correct the problem". This was the beginning of the OctoMY™ project, and while the scope has grown significantly since then, the basic idea is still the same; bring the cool stuff to the masses in an easy way.
OctoMY™ History
Remember the ready-to-run robot software.