Great advice from Phil. On the backend channel I got Mr HACS himself explain why NOT to bother with HACS
(reasons to go straight for a core PR:)
Your code will get reviewed, and when merged it will be available for all Home Assistant users.
I could probably go on and on about issues with publishing a custom_component (with or without HACS), there are somethings that should not be part of “core”, but those are few.
My advice is you should create your integration with the aim of getting it into the “core”, if you want to “betatest” with some form of distrubution system be my guest, but as long as the end goal is to make a PR to have it in “core” why not do it right away by making a PR?
But then on the #devs_general, aside from just feeling like I was learning useful stuff just by reading the banter, I came across an interestingly compelling case to not rely on just doing the PR thing…
paolog89 (10 Jan 2020 at 12:38)
Hello all, I have a really small commit that hasn’t been reviewed since October.
How can I move it forward?
patience paolog89. We’re slowly working through our backlog
Although this is an extreme case I did see a lot of 'can you pull my request please’s so perhaps our answer is to carve out a middle path, doing both! I wonder if I can find a way to keeping taking steps towards a PR for core, whilst happening to pass though HACS on the way there.