search

spgroup / groundhog

A framework for crawling GitHub projects and raw data and to extract metrics from them
http://spgroup.github.io/groundhog
GNU General Public License v2.0
15 stars 10 forks source link

Create Issue entity #35

Closed rodrigoalvesvieira closed 11 years ago

rodrigoalvesvieira commented 11 years ago

Some forges like GitHub and BitBucket have an issue tracker mechanism related to every project. The development analysis of these projects are often directly related to their Issue Tracking activity and thus it certainly represents an opportunity for us to learn more about the projects that we analyse.

Currently, the only Issues-related activity Groundhog performs is the storing of the number of Open Issues per project. Although this is already useful this is far from being satisfactory, since we have forges that correlates Issues to commits, which can provide us much more interesting data.

rodrigoalvesvieira commented 11 years ago

P.S: as of this writing, this issue has a low priority.

fernandocastor commented 11 years ago

This issue is relevant. However, I'm unclear as to what are its concrete goals. How will we know that the issue is solved?

rodrigoalvesvieira commented 11 years ago

Hi professor,

both GitHub 1 and BitBucket 2 do provide a complete API endpoint for their issue trackers. One of the parameters these endpoints provide is the state (in the GitHub API) or status (BitBucket API) which informs the state of the Issue, thus letting us know if it is closed.

Obviously, the integrations is gonna be much more complicated for Google Code and SourceForge. The old annoying fact that we have to crawl their HTML pages to fetch information for the lack of a reasonable JSON or XML API.

fernandocastor commented 11 years ago

What I mean is that the goals of this issue are not clear. We need to be more specific about them in order to be able to determine when we have reached them.

rodrigoalvesvieira commented 11 years ago

Yes, you're right. I'll try to come up with applications for this. Probably by taking advantage of the fact that some forges correlate Issues with commits, thus we can maybe explore how both things evolve in a software project.

If I can't come up with anything clear by next week, then I guess I'll close this issue.

rodrigoalvesvieira commented 11 years ago

Wow, just realized this issue could've been closed more than a week ago.

Anything regarding Issues that is currently pending will be addressed to the Issue https://github.com/spgroup/groundhog/issues/38.