Support/Intern/2011/Brinda/Carrot2: Difference between revisions

no edit summary
No edit summary
Line 102: Line 102:


#Find out top issues the way Cheng does  
#Find out top issues the way Cheng does  
#Use SQL workbench + Carrot2 for the most voted questions to figure out the top issues which should reduce manual reading/figuring out  
#Use SQL workbench + Carrot2 for the most voted questions/popular questions for a particular week to figure out the top issues which should reduce manual reading/figuring out<br>
#Compare how much time the two approaches take
#Are we missing out issues? People might not be voting "I have this problem too" on the same question. It might be spread out over several questions. How can we find a way to club them all together so that it doesn't go unnnoticed?<br>
#Compare which method is more reliable
#How can we use analytics (Web trends, Google Analytics etc) to get a better idea of what the users want?<br>
#Is there a way to find what people are searching on SUMO/ google about mozilla?<br>
#Will looking at User feedback help in anyway?<br>
#Have we tried asking contributors like Corel, Xircal for their feedback on SUMO? They might have mentioned it on contributors forum but is anyone looking at it? Can we use those suggestions since they deal the most with users?
70

edits