Visualizing Open Source Contributions 80
An anonymous reader writes "A student at UC Davis has created some stunning visualizations of open source software contributions, including Eclipse, Python, Apache httpd and Postgres. From the website: 'This visualization, called code_swarm, shows the history of commits in a software project. A commit happens when a developer makes changes to the code or documents and transfers them into the central project repository. Both developers and files are represented as moving elements. When a developer commits a file, it lights up and flies towards that developer. Files are colored according to their purpose, such as whether they are source code or a document. If files or developers have not been active for a while, they will fade away. A histogram at the bottom keeps a reminder of what has come before.'"
lol (Score:5, Funny)
Shit, that sounds kinda scary... flaming files chasing you around the office.
Re: (Score:2)
don't mix it up with the Polka Dotted Armor of Mental Retarding -2.
Re:lol (Score:5, Funny)
Re: (Score:1)
They seem to cover all bases.
Needs flash 9 (Score:3, Interesting)
Re:Needs flash 9 (Score:4, Informative)
Re: (Score:2)
And lest anyone cry, "Open source software will only get better when people use it," get real. Lack of stuff to work on is not the problem with gnash
The good news is that it's a young project that only started in late 2005, so it's far too early to give up on it.
lookatalltheprettycolors (Score:1, Funny)
A bit silly; leaves too many questions.. (Score:3, Insightful)
Cool, and now I start with 1 developer and eventually add more. What exactly does determine where their place is inside the cloud? Does a developer commit and fly towards the middle or is this random? What happens if several developers commit the same file in a quick period of time? I think the idea is fun but I'm not really impressed without knowing these facts too. Without those this is merely a random animation generator based on commits, which can be compared with your standard scope on Amarok.
Re:A bit silly; leaves too many questions.. (Score:4, Informative)
At least that's my interpretation of it from watching the videos.
Can we do this with /.? (Score:3, Funny)
Re:Can we do this with /.? (Score:4, Interesting)
i might even hook up another monitor and have it run as a screen saver and aim it at the hallway - and see who figures out what it is first
Re: (Score:1)
Re: (Score:1)
Your server was coded by a hamster (Score:1)
Your webserver was coded by a hamster and your Perl smells of elderberries!
Re:Your server was coded by a hamster (Score:5, Funny)
Re: (Score:3, Informative)
Ken Coar [apache.org] (no relation to this Ken.)
Re:Your server was coded by a hamster (Score:4, Informative)
Re: (Score:2, Funny)
Re: (Score:2, Funny)
It's a wonderful life (Score:3, Funny)
.
.
.
.
.. but if it breaks the build (Score:2)
Or so one could wish.
That was damn cool (Score:1)
Commits are a bad measure (Score:4, Interesting)
Lots of commits isn't really a measure of developer productivity or worth. Among other things, it might just mean a scatter-brained developer who commits lots of unrelated, mostly useless changes, or somebody who continually writes bugs then has to back them out. More seasoned programmers will tend to make fewer, but larger commits.
Something open source seems to lack in general is project stability. With so little central oversight, changes tend to happen without people really thinking things through, many times without any clear motivation for the change other than simply pumping out code in order to look "active."
Software engineering as a discipline has been working for decades to come up with a heuristic to evaluate programmer productivity, and we're still nowhere close, although there are literally hundreds of formulas in use.
Of course, it's flashy and cool, but I worry that this will only encourage people to make more commits instead of actually using their brains.
Re: (Score:3, Insightful)
Re: (Score:1, Funny)
Re:Commits are a bad measure (Score:4, Interesting)
Re: (Score:2)
It's really not that much different from, say, the mechanical engineer who takes some Newtonian mechanics, pieces from fluid dynamics, some bits from materials science, some core electrica
Re: (Score:2)
Re: (Score:1, Informative)
Well, you could diff... (Score:2)
Re: (Score:1)
In relation to the visualization, this could be misleading, as that person gets credit for the work of all the contributors they select.
In general, this is quite a robust method of development, and most large organizations use it too (the actual job is called "Configuration Manager" or something similar). The difference between open source and commercial development is that the commercial sys
Visualizer is not open source (Score:2)
Pretty, but somewhat useless. The idea is nice and would make a cool presentation on any FOSS project web page, but if it's not open source(d) it'll die.
Re: (Score:2)
Re: (Score:3, Insightful)
Maybe I'm wrong. But "I'll release the code once it's cleaned up" usually means "please don't bo
Irony quotient... (Score:2)
Compared to closed source (Score:1)
Would make great movie credits. (Score:4, Interesting)
Re: (Score:1)
Re: (Score:1)
Re: (Score:1)
Using a contrib. video like this, you could even add a list of each of the contributors and a list of the files each of them patched (instead of the histogram shown in the video).
Neuromancer's Cyberspace Cometh (Score:3, Interesting)
Now if someone could make those visualizations interactive GUIs to archives and people, we might finally be getting somewhere. Someone wake me when we're in Stephenson's Metaverse [wikipedia.org], the home version of the game.
Re:Neuromancer's Cyberspace Cometh (Score:4, Informative)
The one that didn't make it (Score:4, Funny)
Re: (Score:2)
Or on the other hand, the universe is Windows.
I'd like to see... (Score:2)
Likewise, I'd like to see a project that goes through definitive cycles where it has nearly died more than once and then been resurrected.
I have no examples to provide for either of these ideas... it's just what I'd like to see.
Visualizing something useful (Score:1)
I'd like to see... (Score:4, Interesting)
Re: (Score:2, Interesting)
Re: (Score:2)
Re: (Score:2)
Impressive (Score:2)
Open source help. (Score:5, Insightful)
Re: (Score:1)
joke? (Score:2)
Re: (Score:2)
I'm running Ubuntu Gutsy, stock install, so it's not a user agent sniffing issue, unless it's designed only to work in Linux.
Re: (Score:2)
Darn! (Score:1)
Interesting patterns (Score:2)
I'm thinking it's because after a release big architectural, functional, and feature changes are less likely to change really soon and lots of changes have happened recently, so there's a lot of documentation to update and it's the ideal time to do it: the release just came out so
Re: (Score:2)
Re: (Score:1, Insightful)
Hard to understand (Score:1)