-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add feature request link #5324
Add feature request link #5324
Conversation
If you'd like to preview what this looks like, you can have a look at my fork: https://github.com/Mause/duckdb/issues/new/choose |
I am moving those to discussions. Is it possible to have a template here you can't actually open an issue but that just says "open a discussion thing"? |
Opening feature requests as issues is fine as long as we want the issue to be implemented - i.e. you have discussed this with us and we have agreed it is a good idea. That should be clear (and perhaps enforced through a checkbox or similar). We want to avoid people opening issues with "I want DuckDB to have X" - those should be discussions. |
Could try to enforce it by asking for a link to the discussion as a required field? |
Hopefully we'll get proper discussion templates soon: community/community#2838 (reply in thread) |
Looks fine to me - although we might still want to have feature requests with the caveat that they can only be opened either (1) by team members/foundation members/customers, or (2) after discussion with us. I think disabling the blank issues is a great idea though |
Thanks again for making this - we should give these templates a go as people are still confused. |
This is very much a first attempt and probably needs revising
This also tweaks the config to forbid issues not based on one of the two templates, which will hopefully improve the quality of submitted issues