I came across your posting the SEWORLD mailing list. I wanted to inform you of a related project called Hackystat:
<http://www.hackystat.org/>
Hackystat investigates the use of "sensors" such as your Eclipse plugin (we have one too) to collect not only information about developer time in files, but also developer behaviors (so the we can, for example, infer whether a developer is using TDD practices by investigating their patterns of coding and testing).
One thing you might want to consider is: what will you do with this time-based information once you have it? In Hackystat, such data is processed and analyzed by a set of RESTful web services. For example, we have a service called "Software Project Telemetry" that allows the user to learn about trend-based features of their development process. So, for example, they could see if the time spent on coding test cases co-varies with the percentage coverage. This illustrates another feature of Hackystat: we believe that there is a kind of "network effect" in software engineering process/product data: the more different kinds of data you have available for analysis, the more potential for actionable knowledge to come out.
There are a number of ways to interact with our project:
(1) Take a look at our Eclipse plugin <http://code.google.com/p/hackystat-sensor-eclipse/> and borrow any good ideas you find. If you think you've found a better way, please let us know, we'd love to learn from your experiences!
(2) Think about integrating your sensor with Hackystat. Hackystat has a set of APIs which allows it to interoperate with other measurement collection and analysis systems. You could integrate by either sending your data to a Hackystat SensorBase server, which would allow you to, for example, provide trend-based analyses, or by running Hackystat services and sensors in your environment and then having your plugin query them for additional information to combine with your data.
We're always happy to see related efforts. Best of luck to you!
Cheers,
Philip Johnson, for the Hackystat development team
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Philip,
We are very happy of your interesting about our plugin. Your project is very interesting from our point of view and we are honoured to begin a collaboration with you and your team.
We don't know your project, so first we want to see how it works to understand if it's possible an integration or we can only exchange ideas and feedbacks to improve both the applications.
We think that also you don't know JDEEP because it is still a young project but we spent a lot of time to develop it.
So we would like to begin a collaboration, but we must first know how Hackystat works before starting. We can be your tester and you, if you want, can test JDEEP too.
Cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Greetings, all,
I came across your posting the SEWORLD mailing list. I wanted to inform you of a related project called Hackystat:
<http://www.hackystat.org/>
Hackystat investigates the use of "sensors" such as your Eclipse plugin (we have one too) to collect not only information about developer time in files, but also developer behaviors (so the we can, for example, infer whether a developer is using TDD practices by investigating their patterns of coding and testing).
One thing you might want to consider is: what will you do with this time-based information once you have it? In Hackystat, such data is processed and analyzed by a set of RESTful web services. For example, we have a service called "Software Project Telemetry" that allows the user to learn about trend-based features of their development process. So, for example, they could see if the time spent on coding test cases co-varies with the percentage coverage. This illustrates another feature of Hackystat: we believe that there is a kind of "network effect" in software engineering process/product data: the more different kinds of data you have available for analysis, the more potential for actionable knowledge to come out.
There are a number of ways to interact with our project:
(1) Take a look at our Eclipse plugin <http://code.google.com/p/hackystat-sensor-eclipse/> and borrow any good ideas you find. If you think you've found a better way, please let us know, we'd love to learn from your experiences!
(2) Think about integrating your sensor with Hackystat. Hackystat has a set of APIs which allows it to interoperate with other measurement collection and analysis systems. You could integrate by either sending your data to a Hackystat SensorBase server, which would allow you to, for example, provide trend-based analyses, or by running Hackystat services and sensors in your environment and then having your plugin query them for additional information to combine with your data.
We're always happy to see related efforts. Best of luck to you!
Cheers,
Philip Johnson, for the Hackystat development team
Dear Philip,
We are very happy of your interesting about our plugin. Your project is very interesting from our point of view and we are honoured to begin a collaboration with you and your team.
We don't know your project, so first we want to see how it works to understand if it's possible an integration or we can only exchange ideas and feedbacks to improve both the applications.
We think that also you don't know JDEEP because it is still a young project but we spent a lot of time to develop it.
So we would like to begin a collaboration, but we must first know how Hackystat works before starting. We can be your tester and you, if you want, can test JDEEP too.
Cheers