🤷 Ask questions on 💬 GitHub Discussions or 🤦 StackOverflow, not the 🐛 bug/issue tracker

[asvetlov]

💡 This bug tracker exists for tracking the development of aiohttp, not development with aiohttp.

💡🤷💬🤦 Please consider using GitHub Discussions instead — this
is a great place to ask for usage help or show others what you've made with aiohttp. This is where you'd post some generic ideas too.

💬 For live chatting, turn to the matrix space and rooms — #aio-libs-space:matrix.org and #aio-libs:matrix.org (needs an account on any matrix homeserver — matrix.org, gitter.im work, among others)

🤷💻🤦 Stack Overflow is another good candidate for getting a wider community help.

🐛 Only use the bug tracker for reporting bugs and requesting new features.

--
Thanks, aiohttp and aio-libs maintainers.

[webknjaz]

I've made it easier to navigate from https://github.com/aio-libs/aiohttp/issues/new/choose to those external resources.

[asvetlov]

Perfect!
Isn't the list too big?

[webknjaz]

You can make it smaller but I think that important bit is that there's issue buttons at the top and the rest is mostly sorted in the order of importance. People can navigate places w/o having to search for the links elsewhere.

If they are on that page, then they were going to create an issue. With more links there's a better chance that they will not file inappropriate bugs.

Maybe we could improve item descriptions, tho

[webknjaz]

UPD: We also now have a new Discussions location on GitHub — https://github.com/aio-libs/aiohttp/discussions — check it out!

☝️ UPD2: Please use it for everything that is not a clear bug ☝️

[webknjaz]

Reminder: 💬 We also have a space and rooms — #aio-libs-space:matrix.org and #aio-libs:matrix.org on Matrix — these are for chatting live!

Some rooms are hosted on the Gitter.im instance where they were first created (they actually existed there for years), but an account on any server of the Matrix network is sufficient to connect and interact!
I personally use the matrix.org one.