There is no need to delete the current one. Just rename it to “Discussion”.
I never suggested that feature requests continue to be made on the user forum. But a discussion category would be an appropriate place for users to flesh out their ideas with other users before making the formal FR on GitHub.
It’s not getting deleted, it’s getting archived. You’ve made your point, please move on.
What I see happening in the real world (not a devs dream of how it will happen) is that not very many users will add FR’s to github and instead we will see a ton of forum posts like “It sure would be nice if we could have…” in either the config or share your projects sections. And then others will need to point them to github and explain how to use it. then that user might take the time to go there and post the FR that no one else will ever see because normal users never browse GH to look for FR’s to vote for. I know I will never just browse GH for FR’s. But maybe that’s just me.
if the devs are looking for a sure fire way to minimize users interaction with and promotion of FR’s then this is exactly how it should be done.
I can’t say that I know for sure that’s going to be the end result but I really can’t see it going much differently than that.
Yeah, I’m no stranger to GitHub yet when I tried to post a FR this morning it failed because GitHub:
Not a good start.
Yeah HA have implemented some AI detection on the repository and it is not good at all. In fact it’s bad enough that it should probably be turned off.
Odd, I don’t see your duplicate FR. The duplicate detection only occurs after the FR is created by the bot. I only see your single FR, which doesn’t have the dupe bot. Also, the bot didn’t say anything about language (it didn’t even reply on your FR).
Reply to the bot with what it got wrong to train it. Also, as a member (basically a moderator), you’re able to delete the comment and remove the duplicate label. I find it no better or worse than people here marking things as duplicates.
Oh I didn’t know about emails. I’d ignore them, the bot didn’t reply on the FR, so it’s good to go
I just realised there is another problem with this overall approach: there is various threads all over the forum (outside the FR section, e.g. here: Preserve the history of certain sensors for a longer period of time - #2 by 123 ) that mention a feature request and link to it. The problem: with the current plan to archive the FR section in the forum, there is no way to add a link at the end of the thread to the github copy that someone might have created for it. So when people stumble over a FR in the forum somewhere, they have no obvious way of seeing that it “lives on” in github. And to find it, their only option is to use the github search and be lucky.
Is there an option to allow adding a github link to feature requests in the forum that get copied over?
yeah that is truly annoying.
I get those via the Github app, not email though.
btw, I see FR’s being added in the Frontend Discussion section as we speak, shouldnt that be redirected now, or otherwise all of those will leads to yet another group of disappointed users.
Some kind of consistency in the project would be nice.
Nothing has fully transitioned yet or announced, this is a heads up changes are coming announcement thread. Hence why FRs here haven’t been archived. Same with the frontend discussion area.
but that is just silly.
Announce a major change, people follow suit and do as the team suggests, (get funky notifications along with it) because they are warned their existing FR’s in the soon to be archived and henceforth ignored current places won’t be migrated.
Come on, what does the organization want us to do. can’t this be handled properly?
it would be nice if the team thought about waste-of-time concept of their users too.
Heads up changes are coming == decided.
Dude, it’s a work in progress. Sorry, it’ll take time to swap over.
I must say, this is a serous downgrade of user participation. Of course from a developer perspective I do understand that having the feature requests in Github is convenient, but from the perspective of a user adoption it is not. Also; ‘feature requests’ can be solved by others creating a custom integration. The requests in Git only applies to the core.
Please keep thinking community centric towards the HA team, not the other way around!
Note that a representative of dev team participated in this thread only once. Of course they may read posts, but there is a chance that complaining here is just “venting”.
You’re right. But since we are the community, we need to speak. If the dev team doesn’t listen on te long run, the project will die or a fork will appear.
The first post has some text that is blue with a finger pointing at it.
Haven’t been on the forum for a while and was scanning through topics.I happened to bump into this one.
I really liked the Post by @Lakini .This reply completely misses the point.
The way I interpret the long and well informed post was like this: if you are doing something drastic like removing the feature request section,you should really do more than place an announcement and tell people to do it all again somewhere else.
To me,the situation is very typical of what I have seen on multiple occasions from the HA dev team. The impression they leave on me is that they have good intentions and are doing great work but they lack the communication skills necessary to address a large,diverse,critical audience such as the HA user base.
What you are actually upset about isn’t the communication it’s the fact that old FRs will not be imported into the new system. Which will remain the case as the majority of them have not been managed well here and are already either implemented but not closed or there is no intention to ever implement them and they have not been closed.
The new system is managed and this will be less likely to happen. Hopefully.
