@Bhack Exactly. We used to have a ticket on grouped convolution too, and it took more than 2.5 years to close. (Issue #3332 on GitHub, can’t post link here). This one is 6 months old already (it could have been filed much earlier tbh) and I am just concerned history will repeat.

We’re currently working through our issue backlog. Ultimately implementing changes comes down to bandwidth and the volume of requests in the community. It might be more difficult to implement than it looks like on the surface.
Thanks for flagging this thread. I think it’s important to also ensure that further discussion validating this bug happens on the bug thread – that way our triagers and maintainers have full context in a single place. I’ll leave this thread open for now in case maintainers would like to respond here, but may close it in the future to ensure that relevant details and use cases are added to the bug.

I could ask to @thea to check if it the transposed group conv ticket could be labeled as contribution welcome or it is already the internal roadmap.

@Bhack Can you add a mention on the bug that it might be a good candidate for contributions welcome so that can be looked at as part of the ongoing issue grooming work?