Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Addition of a new Question / Query label #4005

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

Closed
raghavrv opened this issue Dec 25, 2014 · 3 comments
Closed

Addition of a new Question / Query label #4005

raghavrv opened this issue Dec 25, 2014 · 3 comments

Comments

@raghavrv
Copy link
Member

To be assigned to issues which are incorrectly assumed to be bugs or for those which explicitly ask a question.

I've seen this being done is another OS project... ( scipy - query )

+ : Searching such questions becomes a lot easier...
+ : Busy maintainers could quickly assign query label to such issues to help other devs distinguish them from an actual bug, even without responding to the issue....
- : It could motivate people to ask questions here, which might not be too welcome...

PS: If this idea is okay... I could help dig up old questions and tag them...

@jnothman
Copy link
Member

Generally, questions are welcome on stack overflow and for more API and functionality-related issues, the mailing list. What sort of question are you thinking of?

@raghavrv
Copy link
Member Author

This is just to label the ones that are posted inadvertently or otherwise as issues at github... not to encourage posting questions here...

For example these could be tagged will query label :
#3927, #3875, #3808, #3818, #3712

and importantly #3825 #3835

( These are just a few issues from the last 1 or 2 months )

The advantage is that super busy devs can simply tag them as query and leave... Interested maintainers can either reply patiently or close... Either case other maintainers / devs looking for real issues to solve can filter these out...

The reason is that, for some issues like #3825, experienced devs can quickly spot them as not-an-issue while a relatively new might take some time to recognize the same... so perhaps filtering them out could help?

I myself am not quite sure about this... :p

Please feel free to close this if you feel this suggestion is not quite useful.... :)

@raghavrv
Copy link
Member Author

On retrospect, I am closing this... feel free to re-open if you feel this is useful in anyway...
Thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants