Re: [mh] Where next with MisterHouse

All

Many thanks for your contributions on this topic, here is my summary;

  * The consensus of opinion is that though 'it isn't broken so we
    shouldn't mend it', it would be desirable if newer languages could
    be incorporated somehow.
  * It is essential that anything we do is cross platform and the
    language most often suggested is Python.
  * This begs the question, if we left the core , could we make it so
    enhancements could  be done in Python? Plugins perhaps?
  * On releases, there wasn't any real objection to having major
    releases as 'stakes in the ground' to signal that the project is
    still alive. I don't think these need to be more regular than
    annually, or if we had a big update (anyone for ia8?)
  * On deprecation, there is no appetite for this, however I do think we
    need some health warnings, you've no idea of how many broken links I
    found when going through the documents. Do a search of the Git Wiki
    for 'Items' and see just how many are unlikely to be developed
    further, or have no manufacturer support any more.
  * It appears several of us have been working on code that is very
    specific to our own environments, and hence not really suitable for
    a pull request, but the techniques may well be useful to others, for
    example several of us in parallel have built Process_item code to
    poll devices and check that they have the expected state, I've
    written heaps on how to make my heating system adaptive to the
    current weather conditions. It would be good to encourage more
    contributions to the wiki, not just code, but also design ideas.

Thanks again

Stay safe

Giles

________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users