With lot of distributions moving forward, what are Neon AI’s plans to support QT6 and I have been informed that your implementation of QT5 won’t just be supported, what are your future plans to support graphical frameworks, or are you dropping support ?
1 Like
I can’t speak for Neon, as I don’t work for them, but my understanding is that Neon and their upstream partner OVOS are interested in both maintaining existing Qt5 GUIs and creating Qt6 options. However, there are no Qt devs on the Neon or OVOS teams, and a very long list of projects to do.
If you are a Qt dev or know any who are up to the task, please do reach out to OVOS and Neon. Any time I’ve spoken to them about this they want to support it but don’t have the resources to do so properly.
3 Likes
A Qt 6 version has been spawned but as @mikejgray mentioned, there is a lack of Qt developers 
2 Likes
While I appreciate your response, isn’t Neon AI the replacement or successor of the MycroftAI organisation? From my understanding, Neon AI purchased or struck some deal with original MycroftAI has been shipping the new Mark 2 units (As I am an original backer of one and running one). MycroftAI, in collaboration with KDE, was previously working to advance the Mycroft GUI, which I was running on my desktop until I decided to update.
However, it seems you mentioned two different projects, OVOS and Neon AI, utilising MycroftAI’s original GUI work without significant progress (What is the connection?). While MycroftAI promised further development, these projects appear to be moving away from GUI development and desktop support. Is that correct?
Additionally, it seems the Mycroft blogs are no longer available, but I found these old links related to KDE’s involvement:
- Mycroft's GUI Goodness
- GitHub - MycroftAI/mycroft-gui: The Graphical User Interface used by the Mycroft Mark II and more
I also noticed that neither Neon AI (previously MycroftAI) nor OVOS (your mentioned project and link) attribute their GUI developments back to KDE or the original GUI developers, does that mean NeonAI no longer works with KDE after the name change from MycroftAI is that correct? There is no mention on either website or proper attributions, but the images for mark 2 still seem to use the GUI framework developed by MycroftAI. However, there is no mention of KDE in the GUI work used by these projects on their websites or are we missing a link there or some support URL?
Lastly, what I also asked about earlier was other GUI frameworks like GTK or HTML? Are there any efforts to replace the work previously done by KDE since no further progress is being made there on supporting newer distributions and it seems you have no further progress there?
OVOS is a community based continuation of mycroft-core, we formed essentially as a distro even before mycroft fully collapsed
Neon AI also predates Mycroft’s collapse, Neon is a commercial company and took over support for the Mark2 and these forums, but they have their own codebase built on top of OVOS (think of OVOS as a library in this case)
when Mycroft collapsed we wrote a FAQ, and i see @NeonClary has continued to edit it so it should be up to date
we also have a detailed timeline of events for everything Mycroft/OVOS, if you want to dig deep into our history that shows how OVOS was born
We have been continuously improving the (python side) gui framework, the original QT gui has been forked under OVOS and is under life support, we only have basic experience with QT and no time to fully maintain the project, but the original author was one of the founders of OVOS and did a bunch of work before leaving, including the ovos-shell used in the Mark2 images (from OVOS and Neon). He also started migration to QT6 but left before finishing that.
As for attribution, the individual repositories as far as we know all comply with the license and are properly attributed as forks, as well has having the appropriate license headers. We also list BlueSystems (who sponsored the lead mycroft-gui developer) in our friends page and prominently mention QT in our docs, PRs welcome if something is unclear
@mikejgray summed up the situation quite well, we want to support the GUI and will give all the help we can, but we need some QT developers to help. The OVOS Foundation never had any official contact with KDE, we would be happy to have a chat and coordinate with others if there is interest and possibility of onboarding some developers!
2 Likes
There’s an important distinction to be made between Mycroft and Neon/OVOS, in that Mycroft had funding to pay full-time developers to work on it. Neon has one full-time paid developer and OVOS has none (although @JarbasAl does work on it full time, it is not his full time job). I contribute to both organizations as much as I can but I have a day job that isn’t involved with voice assistants. For Neon and OVOS to continue to succeed where Mycroft fell off, community support is necessary.
3 Likes