-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move feature requests (& possibly non replicated bugs) to the Anki forums #16189
Comments
My main goals with the move are:
I'd keep in GitHub only triaged issues and accepted feature requests that are specific to AnkiDroid, so all of the issues are actionable |
|
To get the ball rolling, we can change the "enhancements" issue type to point to the Anki forums, and discuss/clean up our current list of enhancements |
I think the move to the Anki forums makes sense. If you need something from me, please be specific. |
Guys, one thing I forgot to mention is that all categories on the forums except the Suggestions and Add-ons categories will auto-close topics after 30 days of inactivity. That's not ideal for feature requests, so please make sure you direct people to the suggestions category. Alternatively, I can turn off the auto-closing for the AnkiDroid group, but that means ephemeral support requests will stick around and can be necroed. |
@dae, could you please create a subcategory for AnkiDroid |
Happy to, but are you sure it's worth it? The desktop version uses a single Help category. The rationale is that users often think they've found a bug when they've in fact misunderstood something. So the help forum becomes a triage area, and when legitimate bugs have been reported, I use a browser extension to quickly create a GitHub issue for the report. |
Okay, so let's test it with just |
Up to discussion if we should leave a bug template in GitHub or not. The goal is to just post confirmed bugs, so most of them are actionable. So, only devs or informed enough people should post bugs in GitHub, and they don't need a template. By not having a template, people are discouraged from creating bug reports here and should go to the forums instead, as they probably won't see or try using the The other option is having a template like Anki, which reinforces that only confirmed bugs should be reported: I'm open to both options, but at the moment I prefer the former. |
Hello 👋, this issue has been opened for more than 3 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically |
We had a discussion on Discord: https://discord.com/channels/368267295601983490/701922522836369498/1228668442794528778
General feeling was that we're getting too many "not planned" issues and should work towards removing the sources, so GitHub only contains actionable requests and we're not doing user support here
The text was updated successfully, but these errors were encountered: