My opinion is that we need a non-wiki based infrastructure for cataloging, tagging, commenting on,  and digesting the thousands of ros packages in the ecosystem as well as hooks into github's and bitbucket's API. 

The prototype infrastructure that we used to generate some of the stats for that talk also hase a built-in web frontend, but I personally don't have time to play web developer. I think the wiki is a great place for unified tutorials and generally static information, but I think we need a more dynamic and structured website to make the packages (and forks of packages) more visible.

If anyone is interested in building more web infrastructure for the ROS community, please e-mail Bill (bill.smart@oregonstate.edu) and myself!

-j