3 ms·

It still takes effort to sort support requests into those he wants to handle and those he doesn't. If he thinks that the manner in which is work is being used

It still takes effort to sort support requests into those he wants to handle and those he doesn't. If he thinks that the manner in which is work is being used is going to bury him with requests, whether he takes them or not, it makes sense to try to avoid the situation altogether. I don't think there's a way to actually do that with an open source project though.

rubatuga 5y ago
I think he’s so focused on time management (from his about page), that he is catastrophizing about the future. He also clearly wants the fame from having a library in Home Automation, but doesn’t want to provide any support.
- jsmith45 5y ago
  He is a paid Home Assistant core developer. (Hired by the company the project's founder created to generate sustainable income for developing the project by offering optional value-add services). This library was written specifically to be used in Home Assistant, as per project policy the code that interfaces with devices needs to live in a separate python package. So there is no real fame to be had from this particular package. He surely sees this repackaging as a source of potential headaches. If the nix folks could convince him that the package would never contain modified code (no no untested/unsupportable modifications), and further that the home-assistant package in nix would always use exactly the version specified upstream (so no version mismatch concerns), he would likely be less opposed. Unfortunately the latter is very much not true right now.
  - lsaferite 5y ago
    I mean, if it's written 100% for HA out of the gate as part of his employment by NC, why wouldn't it just live under a namespace for HA instead of a personal namespace. Using a personal namespace is about building a personal brand at that point.
  - apple4ever 5y ago
    > If the nix folks could convince him that the package would never contain modified code (no no untested/unsupportable modifications), and further that the home-assistant package in nix would always use exactly the version specified upstream (so no version mismatch concerns), he would likely be less opposed. They did everything possible to try to convince him but he had his ears closed and refused to listen. > Unfortunately the latter is very much not true right now. Based on the above, it is very much true.
totony 5y ago
You could put a disclaimer like people on the issue suggested. Nix users are pretty advanced anyway so I doubt he'd get that many useless bug reports.

rubatuga 5y ago

I think he’s so focused on time management (from his about page), that he is catastrophizing about the future. He also clearly wants the fame from having a library in Home Automation, but doesn’t want to provide any support.

jsmith45 5y ago
He is a paid Home Assistant core developer. (Hired by the company the project's founder created to generate sustainable income for developing the project by offering optional value-add services). This library was written specifically to be used in Home Assistant, as per project policy the code that interfaces with devices needs to live in a separate python package. So there is no real fame to be had from this particular package. He surely sees this repackaging as a source of potential headaches. If the nix folks could convince him that the package would never contain modified code (no no untested/unsupportable modifications), and further that the home-assistant package in nix would always use exactly the version specified upstream (so no version mismatch concerns), he would likely be less opposed. Unfortunately the latter is very much not true right now.
- lsaferite 5y ago
  I mean, if it's written 100% for HA out of the gate as part of his employment by NC, why wouldn't it just live under a namespace for HA instead of a personal namespace. Using a personal namespace is about building a personal brand at that point.
- apple4ever 5y ago
  > If the nix folks could convince him that the package would never contain modified code (no no untested/unsupportable modifications), and further that the home-assistant package in nix would always use exactly the version specified upstream (so no version mismatch concerns), he would likely be less opposed. They did everything possible to try to convince him but he had his ears closed and refused to listen. > Unfortunately the latter is very much not true right now. Based on the above, it is very much true.

totony 5y ago

You could put a disclaimer like people on the issue suggested. Nix users are pretty advanced anyway so I doubt he'd get that many useless bug reports.