Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Misc: LAB02-Research vs hass-agent.io #405

Open
shalak opened this issue Mar 8, 2024 · 5 comments
Open

Misc: LAB02-Research vs hass-agent.io #405

shalak opened this issue Mar 8, 2024 · 5 comments

Comments

@shalak
Copy link

shalak commented Mar 8, 2024

What's the connection between LAB02-Research/HASS.Agent and hass-agent/HASS.Agent? I understand that LAB02-Research is the original author, and hass-agent is a fork. If so, why they didn't change the name? It's all confusing now...

@bcutter
Copy link

bcutter commented Mar 17, 2024

Same question came to my mind too when I read #272 (comment).

Hopefully someone can shed some light on this.

I think the most official information is:

https://github.com/hass-agent/HASS.Agent/tree/2.0.1?tab=readme-ov-file#fork

@profucius
Copy link

It appears that the fork is attempting to keep the software alive until the original developer returns to it. They state it in the installer readme. Presumably if/when the original dev (LAB02-Research) wants to resume development, he can merge the fork in and carry on from there. Personally, I doubt this will happen, looking at LAB02-Research's github activity, he seems to have decided to move on in life. So we should be very glad that at least "hass-agent" dev wanted to continue developement.

@bcutter
Copy link

bcutter commented Apr 18, 2024

So... better migrate to the forked version?

@shalak
Copy link
Author

shalak commented Aug 6, 2024

I don't know, the forked version contains binary executables merged into the source code: https://github.com/hass-agent/HASS.Agent/blob/main/src/HASS.Agent.Installer/dependencies/netcorecheck.exe

image

I'm staying with LAB02-Research for now

@bcutter
Copy link

bcutter commented Aug 6, 2024

No idea if that's an actual issue (what's VBA32? never heard about them). Maybe the maintainer of the fork can explain.

But using an outdated, unmaintained and malfunctioning/broken FOSS is also not without risks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants