-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 'community discussion' option for new github issue #3374
Comments
Question is currently playing the role of Community Discussion. I believe we had a community call where we discussed this point, and instead of making 2 new types, we went with Question. |
Let's bring this up as a discussion point on Tuesday |
Looking through the community call notes from April, there is just one line about this with (I assume) @guyjeangilles's name mentioned next to it. Does anyone who attended recall how the discussion concluded? |
It got unresolved, because I had to leave, already being late to something. They said that the questions section is already the community discussion. If I were to finish the discussion, I would've mentioned to just change 'ask a question' to 'questions/community discussion'. Problem solved. |
I think we should stick with the existing "Question"; we have a label for community discussion. The propose to rename as "Questions & Community Discussion" sounds find to me -- happy to review a PR which proposes this change. |
@mekarpeles Questions & Community Discussion is good for me |
Referring to:
https://github.com/internetarchive/openlibrary/issues/new/choose
Problem
There are only options for extremes. Either: 1) put in a request for something to get done or 2) ask a question to get an answer. There's no middle. If there's a middle, where people can put a request for a feature, but not for getting it done - just to brainstorm and it's not a question, it'll help to have an option for that. So I'm proposing a 'community discussion' button.
PS - opening a 'blank issue' is not going to allow the community to see that it requires discussion
Solution - Proposal:
The text was updated successfully, but these errors were encountered: