The Road Ahead - Reintegrating ESH

[rlkoshak (Rich Koshak)]

@Spaceman_Spiff

Please make textual configuration the default way to configurate things! There are so many restraints using gui based configuration and as someone who has to maintain multiple instances this only creates problems.
A nice compromise would be a configuration format which is human and machine readable (e.g. yaml).
The configuration gui could then just create/modify those files. More advanced users can create files directly while newbies could use the gui to create the files.

@Bredmich

Where´s a good place to discuss this topic or things like changes of the oH startup process in oH3?

See Next generation design : Ideas & Discussions for a discussion on this that has already taken place.

The startup process has at least one open issue on ESH’s Github which will presumably be moved to OH during this transfer process.

@Kai

There are plenty of discussions in the forum around those topics already. What is missing is a way to come to decisions

:+1 This. Yes. We come up with great ideas but there is no one to say “yes, do that”. I look forward to seeing what the governance mechanism looks like and what the flow would be from discussions like the one I linked to above would go from discussion on the forum to issue on github to implementation to release (particularly this last part).

As someone who has self dubbed himself the non-technical user advocate, I’d like to be kept in the loop on this. I’ll definitely be watching the architecture topic area.

I think this will be painful in the short term but put OH in a better place for the long term. I look forward to what the future brings! Thanks for the announcement!