Support OpenVoiceOS as Nonprofit Foundation

HUH? How many questions can it answer?

-Mike Mac

You are wrong. You can repeat yourself if you like, and accuse us of closed-mindedness, but we have been here for most of MycroftAI’s history. We do know the details. Dinkum is shiny. That’s all.

I hope that enough OVOS folks can be open-minded enough see this point, not fall into the “not invented here” frame

Tl;dr history of OVOS: Mycroft chases away all its commercial partners and most of its community developers because our stuff was Not Invented Here.

However my experience with NeonOS (and presumably OVOS which underles it) is that it’s a great amateur effort that (please excuse me for saying so) doesn’t come off as that professional, good looking or robust

You’re literally talking to us at our fundraiser.

Indeed, having uncorked the bottle and not wishing to drag this out, I’ll put it this way: OpenVoiceOS’ position on Dinkum before they made it was that it would be the final nail in MycroftAI’s coffin.

And it was, and now its one and only satisfied customer wants us to put the OVOS logo on it. I am truly sorry that a thing you like is doomed, but it is doomed.


Dinkum was created in 3 months or so and started by removing everything the mk2 didn’t need, ovos consists of several different frameworks years in the making, multi platform support has been one of our core guiding principles since the start

Ovos depends on some of the frameworks that were removed or crippled in the making of dinkum, we also have disagreements about the new “sessions” feature of dinkum and don’t think it’s a good idea, in fact it goes directly against some fundamental design choices of core.

I can affirm categorically that OVOS will never fork or maintain dinkum.

I do not intend to criticize dinkum in this post, but want to make clear what our stance and roadmap is, dinkum simply is not in our roadmap or something we care about

1 Like

You must not do many fundraisers. :wink:

I also don’t think the nature of the OVOS Assistant is entirely clear to the public. Certainly it’s more modular than Dinkum, so we’ve failed to communicate at least one thing.

Much of this is our fault, because we haven’t made very many cohesive announcements, but we’ve been waiting on MycroftAI to do that. After they follow up on Michael’s last announcement, then we’ll start carrying on about the technical details, was the idea. That was a month ago.

If the perception has been spread in other channels that OVOS’ backward compatibility represents tech debt, or retention of old code, I would like to emphatically and permanently reject that characterization. Our original mandate, as a dependency for several of Mycroft’s downstream partners, was to remain code-compatible with MycroftAI’s Assistant, not with the entire history of its codebase.

We permanently diverged quite a while ago, as illustrated above. We’ve been deprecating and replacing Mycroft’s limbs, one thing at a time, for years. The guts are probably next. The difference will be that our future overhauls will take place in public, with input and help from our community and from projects that depend on our code. Backwards incompatible changes will never be a surprise.

What we’re trying to set up around ourselves is a reincarnation of the open source community that used to exist around this code.

We have two codebases to choose from as a “starting” point. Both are modular. One is feature-rich, easily extended or reworked, and has always been cross-platform. It also supports historical extensions, while adding a whole new world of extensions using an additional framework, and it deprecates Old Stuff slowly and gently. Its modular nature made it an easy migration for other Mycroft-based projects, and now it’s the basis for all the survivors.

The choice is clear.

I apologize if I seemed confrontational above. It’s frustrating to be having this conversation in 2023. Dinkum and the Mk2 OS represent Mycroft’s second self-fork, and it’s been a very difficult road. Jobs and friendships have been lost over decisions which were forcefully argued, and nobody is happy to have been right. Just frustrated.


The proof is in (the eating of) the pudding. My two cents: don’t announce with words like “Hey! OVOS and Neon can do this”. Rather, announce with videos showing the code actually doing ‘this’. I’m hoping to do a music-playing skill video (soon, Any Day Now :})

Being on the OVOS Matrix channel, has inspired me again. There’s a good vibe over there - people are helpful - and it’s like we know we’re on the cusp of something huge.

Hope this helps.

-Mike Mac

It looks like your goal for this fundraising effort has been met. Is there another goal I can contribute funds towards?

Hi! Thanks for your support, and thanks for asking. We are extending that fundraiser, but we keep hitting our goals faster than we expect. Our full board will chat tomorrow, after which we’ll announce our next target.

I can say that our next goal will most likely be for features, rather than earmarked budgeting, which is to say that the next couple thousand or so will go into our general fund, with a particular eye toward early clerical and legal services. By and large, feature pushes don’t cost us money. They cost volunteer time, so this seems like a good way to balance out a couple of features against the boring likelihood of accountants, notaries, paperwork attorneys, and so forth.

That was where we left things before the weekend. What remains for us to decide is which feature we’ll push for next. I have a pretty good idea what we’re leaning towards, and I’m excited, but I don’t want to tease it until I know for sure it’s what we’re doing.

If anybody would like to donate now, please feel free. The target number will go up during the week, probably by €1.5-3k.


As promised, a campaign update.

New target, new goal: Robo-Personality

We did it! We’ve hit our most recent target, meaning we’ll enter our new life with a budget for a buildserver and boards. Next on the list, it’s time to show the software some love!

One of the great things about coming into our own is our newfound ability to pursue lofty development goals. We’ve rediscovered some old proposals to give the Assistant its first, rudimentary version of a configurable personality. If you’ve been longing to threaten your Assistant with a reduction in its humor parameter, this is the stretch goal for you!

This first version, to set clear expectations, would not necessarily teach the Assistant to crack its own jokes on the fly, which would be a roadmapped extension. This initiative, the groundwork, would teach the Assistant how to choose between a funny response, a flippant response, a flattering response, and so forth, and how to vary these responses to reflect a nuanced personality. It will be up to skill developers and the community to equip the Assistant with things to say, but the same initiative will expand the community’s ability to help with that.

Our next fundraising target is €6500. If this is achieved, the Robo-Personality Initiative will be an early priority after incorporation.

The beginnings of the Robo-Personality Initiative - which will stay on the back burner until Someday, if this stretch goal is not reached, rather than being cancelled entirely - can be followed on GitHub, where the relevant fallback is being designed. Next would be a design period for the needed extensions to dialog files and the skill framework.

We would like to take this opportunity to once again thank our donors, our early adopters, and especially our user-devs for a touching display of confidence. The OVOS team is excited to be expanding and incorporating, even under these somber circumstances, and we take heart in the knowledge that others are interested. We hope our Assistant, once we round the edges, will support you as gracefully and generously as you have supported us.


Minor update: our notary advises us that it would cost us several thousand Euros more to establish the Association than it would cost to create the equivalent Foundation, so we’re going to be a Foundation instead.

This should have no effect whatsoever on our actual operations.

@NeonClary could you please edit the thread title to say ‘Foundation’ instead of ‘Association’? @j1nx will edit the post when he has an opportunity.

edit: Thanks, Clary!

1 Like

our current stretch goal aims to bring to completion the first Persona stable release

this has now been roadmapped in this github issue, links to current WIP also available below