Thank you, Rysiek. "unibrew" wrote : | Another variable in this productization statistics could be how active the project is. It could be based for example on the amount of jira tasks resolved for a month. Or maybe on that how often new versions/upgrades/or whatever are released. | Moreover, activity on user forum and downloads per month might be good statistics. | Yeah, stats you mentioned are really valuable and we are considering them now. These are actually community activity metrics (compare JMM mockup proposed by Damon). Perfectly, we would like to have 3 groups of productization metrics. Let's say: - how easy is to start using product (Please consider name contest as open ;-) ) This would include "packed for download" metric and measuring available project documentation. - support Here I mean professional support services, training and (optionally) activity on user's forums. - project popularity / customer satisfaction The point is, how to measure it. "unibrew" wrote : | Maybe some predefined polls as you mentioned. With questions like: "Do you consider this project a good product?" | | This is mainly documentation but product should have trailblazers, tutorials and other helpful materials for people who want to start using project fast, without reading tons of manuals. | Yes. It came to my mind that polls could be useful not only measuring how product meets users' requirements (customer satisfaction), but these are also a good place to ask them how documentation is helpful (the first group of metrics). What do you think? How about google metric? Seems tempting to measure how popular project is using google search. Cheers, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968320#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...