Probably just my paranoia, but I’m hoping this doesn’t mean the migration away from Discourse. With how the Talent Hub went, an in-house forum software would probably be awful and I (and probably at least 70% of everybody else given how the talent hub went) would 1000% leave
Yes, goal is to use groups for access instead of trust levels. As you indicated that means we’re going to move away from this weird distinction between “Member” and “Regular” where regulars aren’t actually “regulars”, they don’t really get that trust level by “regularly” using the forum, so it didn’t make much sense. Just reiterating there will be a separate announcement for that.
I’m going to follow up internally and let you know, thanks for raising that.
It should be noted that “response” does not necessarily mean resolution, as resolving a bug can take an extended amount of time for various reasons: (not limited to but including)
it might take a significant investment to fix a particular bug compared to the value that fixing it creates, so that’s why it’s not prioritized;
maybe other projects are taking priority over fixing a low-priority bug because the former brings more value to users;
it’s possible that the team has plans to revamp a feature/system that would automatically fix the bug at a later point.
it could be that the issue is not considered a bug from our point of view and is instead the intended behavior;
That being said, the goal is that you should always have an idea of where your bug report is in this funnel, if it’s being worked on or roughly why it is delayed or rejected. We want to be transparent about this and also give you a chance to discuss with us about the reason for a delay or decision not to address a bug at the moment. So thanks for bringing this up again and will get back to you.
We kept the categories separate in the past so that if the bug report wizard ever breaks, there’s still a way to send us messages through those categories. This allowed us to notice a few issues about the bug report wizard in the past where certain users couldn’t report bugs for a while (like here recently).
Additionally since the team working on the bug report workflow itself and the team working on devforum are naturally more active on the forum, it was feasible for us to have those categories open to all, also they saw a lower volume because it was a bit harder to find than #bug-reports.
We have a few projects left earlier in the year to refine the bug reporting workflow further and add more alerting and other safeguards against breakage, and once those are finished, we can likely transition away from those categories and fold them back into the wizard. Thanks for your question on this!
Sorry, but I’m a little confused. Does this mean that Regular will be called something else now? I really do hope so, since I’ve always thought the name was ssuper misleading.
This is really helpful. This will help me, as I have not created any topics yet, and therefore I will now have a section I may start posting a lot of topics in and reporting bugs (if they don’t already exist yet).