Eclipse forge analysis

The Eclipse foundation has setup numerous ways to retrieve information from the various tools and repositories composing the ecosystem. This includes project metadata information, git repositories, bugzilla instances, mailing lists, continuous integration engines, marketplace, sonarQube instances, and much more.

This page intends to list them all and provide examples of usage, in an attempt to foster open data.

Default Primary Success Info Warning Danger


PMI – Project Management Infrastructure

The PMI holds meta-information about all Eclipse projects. It is fully documented on the Eclipse wiki.

More precisely:

  • 275 projects are registered.

SCM – Software Configuration Management

Eclipse uses git for configuration management. Each project can have zero or more git repositories. Data is retrieved from the dashbaord initiative, which in turns uses the metricsGrimoire tool to compute metrics on git repositories. This file has 240 recorded projects.

Commits

2310K
Total
159K  
Year
9930  
Month
1613  
Week


Authors

10704
Total
3355  
Year
966  
Month
431  
Week
  Download
  •   All projects static (light version)
  •   All projects static (full version)
  •   All projects evolutionary (monthly evolution)


This plot shows the evolution of commits across the years for major projects, i.e. projects that represented at least 0.2% of the commits made during last year (70 projects).


ITS – Issue Tracking System

Issue tracking system is composed of bugzilla instances of Eclipse. Data is retrieved from the dashbaord initiative, which in turns uses the metricsGrimoire tool to compute metrics on bugzilla instances. This file has 235 recorded projects.

Closed bugs

277K
Total
57K  
Year
4228  
Month
748  
Week


Closers

8530
Total
2228  
Year
565  
Month
248  
Week
  Download
  •   All projects static (light version)
  •   All projects static (full version)
  •   All projects evolutionary (monthly evolution)


This plot shows the evolution of opened bugs across the years for major projects, i.e. projects that represented at least 0.2% of the opened bugs during last year (66 projects).


MLS – Mailing lists

Developer mailing lists are used by projects to coordinate and exchange about development topics. Data is retrieved from the dashbaord initiative, which in turns uses the metricsGrimoire tool to compute metrics on bugzilla instances. This file has 235 recorded projects.

Sent emails

793K
Total
59K  
Year
0  
Month
0  
Week


Senders

50362
Total
5012  
Year
0  
Month
0  
Week
  Download
  •   All projects static (full version)
  •   All projects evolutionary (monthly evolution)

This plot shows the number of email sent across the years for major projects, i.e. projects that represented at least 0.2% of the number of mails sent during last year (65 projects).