This is a question post, but it’s more specific than my post. It’s asking groups what their needs are, which will result in different answers than the sorts of ideas I provided.
The ideas I gave weren’t ones that were explicitly asked for. They were instead ones I’ve noticed, and, having spent a while investigate, think they would be good bets. Many are more technical/abstract than I’d expect people would understand, especially when thinking “what are my software needs”
In my experience, this is one nice way of coming up with ideas, but it’s definitely not the only way.
I think this might be getting into the weeds though. The TLDR is that I expect that this question will be useful for surfacing a subset of ideas from the community, but it doesn’t seem like the be-all-end-all of feedback for software projects.
I don’t think I understood:
This is already a question post (thanks to Nathan for suggesting it)
Do you want to pick what to work on based on upvotes? I don’t think I’d do it that way (or maybe I didn’t understand you?)
Sigh… sorry;
This is a question post, but it’s more specific than my post. It’s asking groups what their needs are, which will result in different answers than the sorts of ideas I provided.
The ideas I gave weren’t ones that were explicitly asked for. They were instead ones I’ve noticed, and, having spent a while investigate, think they would be good bets. Many are more technical/abstract than I’d expect people would understand, especially when thinking “what are my software needs”
In my experience, this is one nice way of coming up with ideas, but it’s definitely not the only way.
I think this might be getting into the weeds though. The TLDR is that I expect that this question will be useful for surfacing a subset of ideas from the community, but it doesn’t seem like the be-all-end-all of feedback for software projects.
I agree, this is only an attempt to surface a subset of needs that (I’m guessing) don’t currently have a good way to surface.