Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ide-dev] Getting feedback on IDE


With all due respect you need to keep it simple and demonstrate this group can get results. If this list can't agree to 3-5 simple survey questions then how will you make any progress on a better Java IDE.

My offer still stands, send me 3-5 questions and I will get you results in 2 weeks that can be used for the JDT Luna plan.


On 19/11/2013 10:17 AM, Mickael Istria wrote:
On 11/19/2013 09:57 AM, Ian Skerrett wrote:

Can I suggest you guys focus on deciding what will be the survey questions and how you will respond to the results. I can guarantee you will get enough results to any question that will satisfied any statistician. However, if nothing happens based on the community feedback then people will stop giving feedback.

Contributors must be able to contribute questions to the survey when they want, and the survey should be updated consequently everytime a new question is contributors. Those question will be contributed whenever community feedback is necessary to drive a bug resolution. This is pretty useful for "opinion" bugs where feud between contributors can happen very fast. I gave some examples of questions at
Each question should be attached to a bug (ie question entry in DB must reference bug), and the question is removed when the bug is closed.
After enough vote, one of the contributors would look at the result and comment saying something like "Currently we have 884 out of 1243 users who prefer Red to Blue, so let's switch to Red by default".

The idea is that with this approach, contributors can go to the bug, see question results, and decide how it will drive implementation. Also it would be a continuous feedback always at the same URL, not a one-shot feedback with a new URL everytime there is a new question.
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

ide-dev mailing list

Back to the top