To access SourceKibitzer’s DOAP/FOAF services, you can use the following URL’s:

http://www.sourcekibitzer.org/ProjectsRDFList.ext
Returns a RDF Bag with the links to DOAP profiles of all OSS projects registered on the portal.

http://www.sourcekibitzer.org/ProjectDOAP.ext?sp=SprojectName
Returns a DOAP profile for the specified project. You can also navigate to a project page and click on “DOAP” button to get the profile.

http://www.sourcekibitzer.org/BioFOAF.ext?sp=luserId
Returns a FOAF profile of a user with specified ID (a number). You can also get the profile by clicking “FOAF” button on user’s Bio page.

DOAP

DOAP (Description Of A Project) is a RDF vocabulary to describe open source software projects (like ?ne, I once tried to invent myself). This is how typical SourceKibitzer DOAP looks:

<?xml version="1.0" encoding="UTF-8"?>
<doap:Project xmlns:doap="http://usefulinc.com/ns/doap#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<doap:name>Memoranda</doap:name>
<doap:homepage rdf:resource="http://memoranda.sourceforge.net/"/>
<doap:description xml:lang="en">
Memoranda (formerly known as jNotes2) is a cross-platform
diary manager and a personal project management tool.
</doap:description>
<doap:developer rdf:resource="http://www.sourcekibitzer.org/BioFOAF.ext?sp=l12"/>
</doap:Project>

Actually, DOAP vocabulary provides a lot more properties for project’s metadata, but there is a basic subset, derived from SK inner data model (it would be extended in future, I think, to be compatible with full DOAP semantics).

FOAF

Take a look at doap:developer properties – these are the links to FOAF (“Friend Of A Friend”) “foaf:Person” profiles of the project members, registered on the portal. FOAF profiles are RDF versions of the existing user Bio profiles, including backlinks to the user projects (DOAPs) as foaf:currentProject properties. Also, as a tribute to Social Networking philosophy, a FOAF profile is linked to all colleagues of the profile’s owner (with foaf:knows property) – that is the people working on the same projects:

<?xml version="1.0" encoding="UTF-8"?>
<foaf:Person xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<foaf:name>Alex Alishevskikh</foaf:name>
<foaf:givenname>Alex</foaf:givenname>
<foaf:family_name>Alishevskikh</foaf:family_name>
<foaf:title>Open Source Software Developer</foaf:title>
<foaf:holdsAccount>
<foaf:OnlineAccount>
<rdf:type rdf:resource="http://sourcekibitzer.org"/>
<foaf:accountName>alexeya</foaf:accountName>
<foaf:accountServiceHomepage rdf:resource="http://www.sourcekibitzer.org/Bio.ext?sp=l12"/>
</foaf:OnlineAccount>
</foaf:holdsAccount>
<foaf:currentProject rdf:resource="http://www.sourcekibitzer.org/ProjectDOAP.ext?sp=Smemoranda"/>
<foaf:currentProject rdf:resource="http://www.sourcekibitzer.org/ProjectDOAP.ext?sp=Ssourcekibitzer"/>
<foaf:knows rdf:resource="http://www.sourcekibitzer.org/BioFOAF.ext?sp=l8"/>
<foaf:knows rdf:resource="http://www.sourcekibitzer.org/BioFOAF.ext?sp=l20"/>
<foaf:knows rdf:resource="http://www.sourcekibitzer.org/BioFOAF.ext?sp=l119"/>
</foaf:Person>

So, an external agent can get an info about every developer of a specific project, and then learn which projects a given developer has, and who are his colleagues on those projects. Kinda Semantic Web stuff, huh?

This decision seems to be related with recent turn of portal orientation towards a community-oriented service. As SourceKibitzer’s CEO Mark Koffman told me, “we are moving from software towards the people behind it”. Recently, the portal has launched new features to support this direction, namely online resume for Open Source community members (Bio) and series of interviews with OSS developers.

I think, it has good chances to grow into a real social network for the FOSS folk.

At the moment, the portal code is published under GPL v3 Draft. An exception is the proprietary libraries implementing the benchmarking algos, which are know-how of the company running SourceKibitzer. The portal invites everyone to join the development by subscribing the mailing list , participation in TRAC Wiki and contributing the code into SVN repository. The portal technology is based on Java Spring framework.

What is SourceKibitzer

SourceKibitzer is an online service for automated (so, unbiased) assessment, analysis and benchmarking of Java source code. For the moment, over 500 open source Java projects are analyzed (including, e.g. the whole Jakarta pool) and Kibitzers plan to “Measure all available Open Source projects written in Java”. SourceKibitzer works directly with CVS and SVN repositories to monitor the code development, so the reports are always in actual state.

SourceKibitzer methodology contains a number of various metrics and many of them are really useful and interesting.

Progress analysis
It is similar to Sourceforge “project activity” info, but on more detailed level. Kibitzer’s report contains progress information for each compilation unit (a package or even a single source file) – how many statements, methods and comments were changed during the last week.

Size analysis
Gives the total numbers of lines, statements, methods and comments in each package and source file.

Complexity analysis
It evaluates code complexity by measuring different metrics: the number of instaniations of classes (“Data Abstraction Coupling”), the number of classes given source file relies on (“Fan Out Complexity”), the number of possible execution paths through the methods (“NPath Complexity”), McCabe’s cyclomatic complexity of the methods and boolean expressions complexity.

Completeness analysis
It is based on assumption that number of conventional “todo labels” in the comments (“TODO”, “FIXME”, “XXX” etc) and total comments density mean the level of project’s maturity.

Kibitzer’s team say they are working on improving the methodology and plan to implement more metrics measurements in the future. You can submit your own Java project to kibitz it.