Posts Tagged ‘open source’

21, Sep 2008

Diving into HackyStat

What is HackyStat?

  • Hacky – Something definitely related to Software.
  • Stat – Statistics. Software Statistics. Software Telemetry.

HackyStat is a framework for advanced software telemetry.  When you can monitor many chronological aspects of the software, you can have a fine grained view about where the project is proceeding! The idea is to, non intrusively, collect as much data as possible about various matrices in software development.

How old is the project?

It has been under development since 2001. But just went a major re-write. Presently at Generation 8.

What does it do.

Here is a simple explanation.

  • Many Tools collect various data.
    • Your code coverage report.
    • Unit testing report.
    • Code Churn
  • Sensors collect this data from client installation. send over to sensor base at a server.
  • There are other servers, that talk through RESTful APIs to this sensor base.
  • You can create/design your own web/service to have further insight into the collected data.

The Architecture

  • This is not a basic client server technology.
  • This is a RESTful architecture.
  • Many servers. Many Clients.
  • Everything doing just “a small plain simple job” but together many things.

What can it do for you?

(Copied directly from http://code.google.com/p/hackystat/ )

Hackystat is an open source framework for collection, analysis, visualization, interpretation, annotation, and dissemination of software development process and product data. The Hackystat Framework supports three software development communities:

  • Researchers. Hackystat can be used to support empirical software engineering experimentation, metrics validation, and more long range research initiatives such as collective intelligence.
  • Practitioners. Hackystat can be used as infrastructure to support professional development, either proprietary or open source, by facilitating the collection and analysis of information useful for quality assurance, project planning, and resource management.
  • Educators. Hackystat is actively used in software engineering courses at the undergraduate and graduate levels to introduce students to software measurement and empirically guided software project management.
More to follow. :)
Comments awaited. :)
technology, , , , , ,
No Comments
Posted By Meera
2, Sep 2008

Google Chrome – Traces of Firefox3 within

In my previous post,  Google – Ready to take over the web, about Google launching a Brand new browser, based on other already existing open source technologies.

I just tried it. (This post is being written from Google Chrome). The UI is the same as described in the Comic book. People who have used FireFox 3, would be pleased to see the “refreshed” bookmarking facility, that also shows google quick search results.

Update: Official Google video (1Hour)
 Google announcement

technology, , , ,
No Comments
Posted By purnank
28, Jul 2008

Jupiter Plugin for Code Review

There is a great open source Eclipse Plugin for Code review – Jupiter. The User Guide is now available in PDF Format.

Jupiter Eclipse Plugin has a very good integration with your IDE and your configuration management system. If you are not using any IDE, this is the right time to start using Eclipse.

If you are not using any configuraiton management system, please tell me how you can still work withing a team. More about usage of Jupiter would follow.

More about installation has been very well documented at wiki page with google code.

Here is a short note on how to perform a review using Jupiter.

  1. Initiate a review.
    1. Name the review.
    2. Select files for review (Optional)
    3. Select users who would participate in review (Necessary)
  2. A “review” file would be created/appended. (This file is in XML format)
    1. This file would be one per project. (Remember project. Not folder/file. One project, one such file. This may be a micro limitation for very huge mis-orgranized projects.)
    2. Share this file with all peer developers through configuration management systems.
    Jupiter Plugin for Code Review
  3. Ask peer developers to pull in changes from configuration management system.
  4. Now peer developers/reviewers should press the Purple Button with Jupiter symbol.
  5. Now three stages of review would be performed.
    1. Individual
      Just collect the comments. Question is What is the issue?
    2. Team
      Question is who is going to address these comments?
      Just make sure that in the end one person works on one file. Do not assign same set of source file to multiple developers. Else when you merge developer changes, line number mismatch is destined to happen.
    3. Rework Phase
      Now address the comments, and fix them.
  6. At the end of all the three phases, you will have to push in changes to configuration management.
  7. It is suggested to have these three phases, as discrete as possible.
  8. Don’t forget the Golden sentence, “One developer, one source file to fix issues“
  9. Close the review (Remove un-necessary files from configuration management system).

Jupiter Users Group

I and the Jupiter user group would be very happy to address your issues comments.
http://groups.google.com/group/jupiter-users

Feature Update Site

You can directly use this update site within your eclipse to update the eclipse plugin
http://jupiter-eclipse-plugin.googlecode.com/svn/trunk/site/

technology, , , , , , , , , , ,
No Comments
Posted By purnank