scheff1
(scheff1)
4
Yes and no. If I remember it correctly, HDS was first released in September 2019. Spiceworks intended at that time to develop HDS and CHD in parallel unto close to feature equality with the desktop edition before retiring the desktop edition. So both were expected to become successors, keeping the choice of public Cloud solution and on-premise solution. And as HDS was just a port of CHD, almost no additional development resources would be needed.
I don’t know when Spiceworks changed its mind without indicating it as a change of mind. At some time, the CHD documentation updated its FAQ section and reports that CHD (and HDS) not only have no feature equality with the desktop edition, but additionally promised to never reach feature equality. So those awaiting feature equality before considering a migration to whichever solution did not get notified of such change of mind.
You already read the first official announcement of Spiceworks back in May 2021 where Spiceworks obstructed its previous plans to make HDS a successor by announcing suspension of its active development, obstructing its initial reason and motivation to create HDS at all. When HDS is just a different output of common code base for different deployment, the automated build process and the automated regression test process would ensure that resources needed would be limited to time and storage. But in that announcement of May 2021, Spiceworks considered that HDS would bind too much undisclosed resources and undisclosed adoption rate was below undisclosed expectations of Spiceworks, omitting any root cause analysis (if most organizations delayed adoption due to lacking feature migration to HDS). That’s also called self-fulfilling prophecy where the prophet announces future events which were caused by the prophet and its announcement.
And you were even replying to this first official announcement although your assessment of privacy was too simplified and hence wrong in its simplification. Your privacy assessment was contrasting Spiceworks privacy statements for HDS. So if you would have done the privacy audit correctly in 2021, you would have known that even HDS would not meet your privacy requirements. It was already subject of a topic on HDS privacy back in 2020, and repeatedly afterwards.
So the announcement referenced by Conor is the 2nd official announcement, turning the initial suspension into expected end of development, and announcing an end date of support in addition which was end of last week resp. Spiceworld 2022.
I have not yet decided. My focus is on inventory, not on ticketing. I’m considering GLPI IT and Asset Management Software. And it is coming with a ticket system, having also an option and integration for at least another alternate ticketing system. It is available for on-premise as well as Cloud based.