Queries and visualizations to help people use data

Apache Camel data

We have released several files of Apache Camel IRC log data.

originally stored by Dan Kulp
More about Apache Camel

Related Data Sets
Apache Twitter Handles
Apache Project People & Roles

Sample Queries for the IRC data:

Data Resources: 

Freecode New Project Registrations (1998-2011) and language tags

This chart shows the new project registrations for each year 1998-2011, and what programming language those projects were tagged with.

For example, 2003 was the highest year for new "C" projects to be registered with Freecode (then called Freshmeat).

Data Resources: 

Objectweb Project Licenses, July 2012

Objectweb allows each project to state what license it uses. Here is a chart showing these licenses for all the projects on Objectweb, as of July 2012.

Data Resources: 

Rubyforge License Counts, July 2012

Each project on Rubyforge can list what license it uses. The following chart was generated in July 2012 (datasource_id=317) to show the most common licenses (all those with more than 10 projects using it) and how many projects.

Data Resources: 

Tigris License Counts, July 2012

Tigris lists the open source license that each project is using. The following chart shows the licenses used by projects on Tigris, and how many projects use each. Note that UNLIKE some other forges, variations of the GPL (and other licenses with multiple versions) are not differentiated by version, rather they are all lumped together.

Data Resources: 

Freecode Project Dependencies, July 2012

Freecode allows each project to declare which other projects it is dependent upon. Here is a chart showing the projects that were declared dependencies most frequently. PHP was the project selected most often by other projects as a dependency.

Data Resources: 

FSF Network of Required Projects, July 2012

FSF allows each project to state what other packages are required by this project.

Here is the SQL code to generate the data showing which software packages are most commonly required by other projects.

Notes: (1)We also have data on the TYPE of requirement (use requirement, build requirement, etc), but this column is not used in this query. (2) The required project does not have to be listed on the FSF directory to be included in the list. (For example, Perl is the most commonly required package, but this is not a FSF-directory listed project.)

Data Resources: 

FSF Network of Related Projects, July 2012

The Free Software Foundation directory (FSF) allows each project to list other FSF projects that are related to it.

We could construct a social network showing what projects are related. Here is the SQL code needed to make the list of what projects are related to what other projects:

SELECT pr.proj_num, p.proj_unixname, pr.related_project_name
FROM fsf_project_related pr
INNER JOIN fsf_projects p ON p.proj_num = pr.proj_num
WHERE p.datasource_id=[current datasource_id]
AND pr.datasource_id=[current datasource_id];

Data Resources: 

FSF Count of Projects by License, July 2012

FSF requires projects to list a license under which the project is released. This chart shows the top 25 licenses. Note that there is an "Other" category (211 projects) that includes ALL other licenses AND projects that chose "Other" as their actual license choice. This chart was generated using the licenses listed for projects in July 2012 (datasource_id=319).

Data Resources: 

FSF release dates, by month and year (as of July 2012)

The Free Software Foundation directory lists free software projects and pertinent information about those projects.

One of the items we collect is "released on" date. This information refers to the last release date for the software, as reported in the FSF Directory.

This graph shows the aggregated release dates for the 6855 software packages listed in the FSF directory during the month of July 2012 (datasource_id=319).

Data Resources: