Forums : Suggestions for Ohloh 2.0

Dear Open Hub Users,

We’re excited to announce that we will be moving the Open Hub Forum to https://community.synopsys.com/s/black-duck-open-hub. Beginning immediately, users can head over, register, get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.


On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at [email protected]

Add Issue Tracking statistics to the projects

Would it be possible to add link to issue tracking systems (bugzilla, jira, etc) to those projects that have issue tracking and provide some statistics about it as well (like, how many issues reported in last month, mean time to first reaction, mean resolution time, etc)? It would definitively provide some additional info about different projects and teams working on them.

Jan Haderka over 16 years ago
 

already discussed here

dartar over 16 years ago
 

Sorry, wasn't too obvious from the topic of that discussion that it is about same topic and search over posts for 'issue tracking' returned no results.

Jan Haderka over 16 years ago
 

hi rah003, no probs—it was just a similar proposal I made in the context of a totally off-topic discussion.
Thanks for bumping this request which I'd really like to see implemented.

Trac should obviously be added to the list of issue trackers to be considered.
I'm not familiar with Bugzilla or Jira, but Trac allows full exposure of its ticket DB through XML-RPC so it shouldn't be difficult to retrieve and analyze data from existing Trac repositories.

dartar over 16 years ago
 

Greetings all,

Adding more types of project data feeds is on our roadmap. So far we're considering:

  1. Issue Trackers
  2. Mailing Lists

I'd like your opinion(s) on which to target first. I'm personally leaning towards mailing lists first. My reasons are:

  • Mailing list traffic is a better gauge of a project's health (imho)
  • Mailing lists reveal better social interactions between people (you tend to converse with 'friends')
  • Many projects use mailing lists as bug lists
  • It's easier to write (one protocol)

Whaddya think?

Jason Allen over 16 years ago
 

@dartar
Yeah, of course, Trac should be in as well. Didn't meant that list to be exhaustive.;) XML-RPC access is good. Jira supports it as well (when enabled) and I tend to use it quite a lot.

@Jason
Personally I've no preference, mail list or issue trackers are both interesting and important. Actually I find quite interesting what you outlined ... look for who's discussing with whom and I guess people would tend to join the discussion on topics with certain keywords only. I've done bit of this myself having written small tool looking over forum archives for correlation between keywords and authors of various posts ... it can be quite a fun. So if it is easier to go for mail lists then go for it.
Another thing which could be done in the future is to try to get some insight into build process. I would guess quite few projects have some kind of online continuous build system listening to changes in repository and then building the stuff and executing all tests ... could be interesting to peek into results of those as well.

Jan Haderka over 16 years ago
 

Mailing lists may be one protocol, but how are you gonna extract necessary info from them? I figure you need to get web archives of them (crawler style), but then there are many different softwares producing archives... or are you going for raw mbox?

One alternative is of course to base it on mailing lists retrievable from services such as gmane.org...

Daniel Stenberg over 16 years ago
 

Mmmm, I doubt extracting data from mboxes is on the cards ... interesting point though ... mailing lists may be one protocol, but mailing list archives aren't.

Daniel / Nazca ... over 16 years ago