Visualizing Open Source Contributions
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.'"
"When a developer commits a file, it lights up and flies towards that developer."
Shit, that sounds kinda scary... flaming files chasing you around the office.
Are there other sources for the videos for us Gnash users?
If a file is commited it flies towards the developer
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.
Finally, a way to see who is wasting the most of their day here!
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
"Flag on the moon. How did it get there?"
"When a developer commits a file..." an angel gets its wings. .When it breaks the project, the angel and developer go to hell.
.
.
.
.
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.
I'd like to see that type of presentation used to show the credits for a film. You could color the contributions according to acting, camera, sound work, directing, etc.
Apparently they did the same thing for Vista and posted it to youtube, but people just thought it was a watermelon exploding...
Support microSD: in a post 9/11 world, it is unwise to carry your data on media that you cannot comfortably swallow.
Linux kernel, Free/Net/OpenBSD, gcc, ... the core infrastructure