A Visual Look at Fishworks
By cindi on Dec 02, 2008
So what does a project like Fishworks look like?
I put together a visual representation of the Fishworks project using Code Swarm that has been captured in a video. The video shows how the Fishworks team and project evolved based on changes made to the source code over the course of two and half years. The code swarm tool uses organic visualization techniques to model the history of a project based on source code files and their relationship to the developers that create and modify them. It's a very cool tool and a bit addictive.
There are a number of code swarm project visualizations available online. The OpenSolaris and Image Packaging System (IPS) projects have been represented by Code Swarm based on raw commit data made to each project. The OpenSolaris Code Swarm pulses as a single blob of source as developers come and go within the orbit of a vast code base. In contrast, the Fishworks project shows well-defined orbits surrounding each developer. This is a testament to the almost constant activity of a small number of developers on a well-partitioned source base. I have elided gate re-synchronizations to better represent the project and the contributions of each developer. This avoids single bursts of activity by what seems to be one developer as seen in the IPS Code Swarm.
Fishworks CodeSwarm from John Danielson on Vimeo
Code Swarm runs natively in Subversion and Mercurial repostitories. The Fishworks project source base was controlled by SCCS with logs created by Teamware. I converted the Teamware 'putback' logs to the Code Swarm input XML format . I do wonder how the visualization would change if I accounted for lines of code changed per file. I might be able to use Eric's code tracking script to generate suitable input.
In the meantime, enjoy the show.