@JMack89427 Dig it. The current repo is owned by you. It looks like it has both 'current' and older versions in it. Something like the
quickGetWaterTemp feature @mike.maxwell is working on could be tracked as a branch and pull request. . . . if people are comfortable with that kind of workflow. I don't want to step on any toes, nor make it harder for people to contribute -- only to organize contributions so they're clear and don't cause regressions, and so people can always find the version they want.
Given my druthers, I would:
- Introduce a 'readme' with details about what is fixed in each version
- Create 'releases' that are tagged versions of the repo so people can readily find the version they want
- Use GitHub issues? Perhaps? To track what is being worked on so the thread doesn't get confused
- Use branches/pull requests to make fixes merging really clear - then people who wanted to work with a branch/beta version could, but others would know what was current and stable.
The latter two I'm unsure about. Are people familiar w/ branching and pull requests? Or would that create a barrier to entry that is too high?
You're the current repo owner, right @JMack89427? (I'm not even 100% sure of that. . . .)
If we did something like this, it could be a natural fit for eventual 'promotion' to eg the
HubitatPublic repo - it looks like that is fairly stalled at the moment, but they do have a repo of contributed code. If we got this stable and versioned, I'd be happy to talk w/ them about how to get this into it once it was complete and stable.
All of this with a big ol' grain of salt - I've been lurking and I think I have a feel for what's happening, but, again, don't want to step on any toes!
Say the word, I'll do the above - let me know what repo to do it in. I could even create a new one with a clear history and versions and make everyone here a contributor/owner.