To be honest, no, I did not see a message indicating that a developer was needed to step forward and avoid having this integration abandoned. At least not before the decision was made to deprecate it and, ultimately, abandon it. If that took place then I’m afraid I missed it.
From what I saw, it was after the decision had already been made that the discussions about it began here. And it was after that when the official notice appeared in the Release Notes. That brought a lot more people into the discussion. Even then, that discussion went on for a while (with much negative energy being expended) before someone stepped in and took it on. (With my unqualified gratitude!)
Here’s the exact text from the Release Notes:
As of this release, all integrations interfacing with GPIO directly, have been deprecated.
There are multiple reasons for this, which includes a general low usage of these integrations. For most Home Assistant installations, GPIO isn’t easily usable and more often the integrations are unmaintained.
There was a note near the end which said:
We welcome custom integrations (existing or new ones) to provide alternatives.
This doesn’t come across as “we want to keep supporting this but need someone to take it over.”
My point was that this last step, announcing that someone was needed to take over support so it wouldn’t have to be abandoned, could have been the first step, before the decision was made, and before anyone (justifiably or not) got upset over it.
I’m only posting here to try to lower the temperature a bit and move the discussion toward ways to avoid this sort of thing in the future. I’m sure we can all agree that keeping this forum civil would be a good thing.