| 12 Jun 2021 |
 Mic92 (Old) | I think also pypi does not allow you to depublish stuff easily | 16:42:47 |
 @hexa:lossy.network | Worst case then would be not submitting tests to PyPi | 16:42:48 |
 lukegb (he/him) | Right. | 16:42:53 |
| @hexa:lossy.network | which is a setuptools kind of thing to do | 16:43:26 |
| @hexa:lossy.network | I don't think pyproject projects usually do that | 16:43:34 |
| @hexa:lossy.network | and yet, there are no tests on PyPi | 16:43:50 |
| @hexa:lossy.network | https://github.com/frenck/python-ambee/blob/main/pyproject.toml#L23-L25 | 16:44:10 |
| @hexa:lossy.network | I'm disappointed that he considers our home-assistant to be "broken" | 16:44:37 |
 @andi:kack.it | What is the stance of the other home assistant people towards what supported systems are? Them running their own distribution is nice but I always feared it will at some point be the only supported way of running it. | 18:33:36 |
 Fabian Affolter | There has to be made a distinction between the Home Assistant Community and Nabucasa. NC would prefer if there is only HassOS. The target audience for HassOS are home users and home users are likely to pay for the cloud integration. | 18:58:06 |
| Fabian Affolter | The community is running Home Assistant wherever they can (NAS, Kubernetes, venv, all kind of operating systems and hardware platforms). Those users often don't want an additional Raspi running and are capable to have remote access in a secure way | 19:00:10 |
| Fabian Affolter | Nowadays, there are three supported installation methods$ | 19:00:38 |
| Fabian Affolter | * Nowadays, there are three supported installation methods | 19:00:49 |
| Fabian Affolter | Sorry, four methods https://github.com/home-assistant/architecture/tree/master/adr | 19:02:22 |
| Mic92 (Old) | They got to be careful so not to mess with there contributors too much. | 19:02:35 |
| Mic92 (Old) | I don't think the average hassos user will improve integrations. | 19:03:00 |
| Fabian Affolter | Indeed | 19:03:51 |
| Fabian Affolter | The regular HassOS user is just a consumer and happy if the lights can be controlled ;-) | 19:04:52 |
| @hexa:lossy.network | The only nixos related contact I had was with the issue tracker, when tests were failing. Mostly racy ones. The message I got was that if it doesn't fail for them they don't want to invest the time to fix it. | 19:05:05 |
| Fabian Affolter | The Home Assistant eco-system has become a bubble. | 19:06:06 |
| @hexa:lossy.network | And since we use highly parallel xdist, while they run their CI on Github Actions, we are going to trigger some weird things | 19:06:16 |
| Fabian Affolter | ...and the GitHub Actions changes in one way or another...schupps, there are the same issues | 19:09:52 |
| Mic92 (Old) | We just need to wait until hass gets more cores :) | 19:09:56 |
| Mic92 (Old) | s/hass/github actions/ | 19:10:04 |
| @hexa:lossy.network | And ultimately no NixOS should think they can get support for home-assistant anywhere besides the NixOS community | 19:12:26 |
| @hexa:lossy.network | unless they disguise themselves properly | 19:12:37 |
| Mic92 (Old) | In reply to @hexa:lossy.network
And ultimately no NixOS should think they can get support for home-assistant anywhere besides the NixOS community Time for a new github identity? | 19:14:35 |
| @hexa:lossy.network | I don't think one would have to go that far. | 19:15:02 |
| @hexa:lossy.network | Just doing ones due diligence that the issue is not NixOS' fault would be good enough | 19:15:36 |
| @hexa:lossy.network | Our packaging is good enough to make most things work reasonabl y well | 19:16:32 |
