Hey guys,
I'm not sure if you are familiar with the kind of studies/reports we are performing in our spin-off named Bitergia. [1][2]

We've just published a report of the history of Fusionforge built with the information available in the Git repository of FusionForge and the mailing lists. I hope you find it interesting/useful:

http://blog.bitergia.com/2012/11/16/the-history-of-fusionforge-and-gforge/

In the following weeks we plan to add FusionForge support to the tool that gathers information from issues (its name is Bicho), so a new version of the report will be generated with more sources of information (commits, mails and issues).

The process to create this kind of report is almost automatic, so you could reproduce it if you want to[3]. Take into account that this automatic process doesn't pay attention to important factors that could affect the final result (unique identities, bots, companies involved, types of commits, etc ..)

Any kind of feedback is really appreciated.

Best!,
Luis.

[1] http://blog.bitergia.com/
[2] http://bitergia.com/public/reports/openstack/2012_09_folsom/
[3] http://metricsgrimoire.github.com/




--
|\_____/| Luis Cañas-Díaz
 [o] [o]  [email protected] - Software Engineer
 |  V  |  http://www.bitergia.com
  |   |   "Bridging the gap between developers and stakeholders"
-ooo-ooo-

_______________________________________________
Fusionforge-general mailing list
[email protected]
http://lists.fusionforge.org/cgi-bin/mailman/listinfo/fusionforge-general

Reply via email to