or how to replace git push heroku master and cf push with Kubernetes
PaaS has made deployment of applications very easy. Kubernetes has made deployment of applications very flexible but not easy. There are efforts to add the "easy" part to Kubernetes. That would make Kubernetes a good alternative to PaaS. With so many public cloud Kubernetes offerings nowadays, it would be nice if one could simply pick up their preferred cloud and have an app running in minutes. This HackWeek project will be and exploration of the available tools that can make Kubernetes as friendly as a PaaS for deployment but also how much Kubernetes can help development.
There are various home assistant solutions out there but all of them transfer your voice to some server for processing. This is a no-go for sane people although the technology is interesting and could be useful. There are various open source tools out there to achieve the same result but there is no turn key open source self hosted solution. The goal of this project is to implement a way to have a home assistant running locally - ideally with one command.
The project that is closer to the desired result is Mycroft (https://mycroft.ai/). It is very easy to run the client side components using one docker command but their backend is running remotely. All the tools they use though are open source so it only needs one to do the work and package them in a nice little docker-compose file (https://mycroft-ai.gitbook.io/docs/about-mycroft-ai/faq#can-mycroft-run-completely-offline-can-i-self-host-everything).
I was talking with a friend the other day who is blind. He briefly explained to me how he reads books (the regular, paper printed ones). So, he is taking a photo of each page, passes that to the OCR to extract the text in digital form, then passes that to some text to speech engine to read it out loud.