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]

I'd like to see bug tracker activity ...

I'd like to see bug tracker activity monitored as well. Bug reports are the way most people get involved into open source projects for the first time. Many commits to a project originate from a bug tracker and were written by someone other than the cvs/git/svn committer.
Maybe there are even some nice ways to query bugzilla, flyspray et al.

And, by the way, is there a way to search the forums for things that have already been suggested?

LYRIKpage about 16 years ago
 

Yes, our original vision for Ohloh included the ability to monitor bug trackers as well as mailing lists. Once we get a handle on source code monitoring, bugs and mail are in our plans.

Forum search is possible, but it proves to be very hard to find. We're working on a site redesign now which will help here.

This page has a forum search box.

You can also just search in the box at the top of any page. It will take you to project search results by default, but from there you can click Posts to see forum search results instead.

Robin Luckey about 16 years ago
 

Is there any timeline for this?

I've come across some corporations which really would like an easy way to address this, and in fact at mozilla.org, a non trivial amount of triage time is spent trying to find the tracker for various extensions/plugins/random applications which each have their own hard to find web sites.

I'd really love to be able to simply visit ohloh and get a link to the bug tracker. Even if the bug tracker isn't searchable.

I understand that at the beginning I'd probably be filling in the links more often than I'd be finding them, but this really doesn't bother me.

It's also not immediately important for me to be able to use ohloh to search the bug tracker, although I recently described to a large entity how such a feature could be useful.

And yes, Mozilla projects are still waiting to see Mercurial support from ohloh, but we're already growing tools to handle Mercurial. We don't have much interest in growing a tool to map the world of software projects to record where their bug trackers live - this is something that I eagerly await from ohloh.

timeless over 15 years ago
 

I'd just like to add my support for this idea. Our project has many contributors who submit bug reports and patches on a regular basis, but myself and a couple of others claim their work here on ohloh.
Also I'd like to suck up some kudos for my fleeting visits to other projects trackers :D

Gaz Davidson about 15 years ago
 

Yes, having this feature would be great.

Any update on the timeline ? It's been a year since it has been suggested.

Vincent Petry almost 15 years ago
 

I'd just like to add another support for this idea, I can't agree more with Bug reports are the way most people get involved into open source projects for the first time. ;-)

Four years gone after the original post, is there any process?
I understand the ohloh guys are busy at this time, maybe a patches welcome is nice as well ;-)

I checked https://github.com/blackducksw/ohloh_scm but it seems not related to bug trackers, any one know if there is a similar library for bug trackers at this time?

Keep up the great work and thank you all!

Cheers.

Qian Hong over 11 years ago
 

I would love to see this happening as well. It would be a valuable asset to highlight project activity. I tried some software to get statistics for our project based on Trac but no one really convinced me. A system analyzing Github, Sourceforge, plus Trac, Jira and Bugzilla instance would be useful.

Don-vip over 9 years ago
 

I want to add my support for this idea also. Although I do plenty of coding of my own, I have chosen to specialize in bug testing for other projects, and I've ranted liberally about how unappreciated bug hunters are in general. You can read my rant here:

https://www.mediawiki.org/wiki/User:Badon

It would be very helpful if there were some way to keep score of all of my reported bugs that were resolved as fixed, versus the ones that were resolved as invalid, duplicate, or wont-fix. Having a way to keep score would put bug hunters lightyears ahead of the dung heap they're often relegated to at the present time. This is a huge ongoing cultural, managerial, and technological problem that OpenHUB could single-handedly reverse.

From a competitive business point of view, giving some attention to the bug hunters would immediately distinguish OpenHUB, because no one else is doing it, nor do there appear to be any believable plans to do it. After 7 years, it's clear that OpenHUB has no genuine interest in pursuing this idea, but I hope what I've said above can persuade you that this is important unexplored territory that could yield surprising or unexpectedly positive results.

If it's true that most developers begin as bug hunters, then something like this could change the world. What if the Bill Gates vision of school children all being taught software were to come to fruition indirectly, by starting them off with reporting bugs and exercising the critical-thinking skills required to make a good case for a new feature they're requesting?

badon over 9 years ago
 

Well, I think bug tracker statistics are very hard to generate because OpenHub has no access to the DB (while they have the complete data available for source code repositories). Also there are even more bug trackers than version control systems so it's also more effort.

My guess is that they'd like to do it but currently the devs are still working on fetching repos on a regular basis, eliminating stuck jobs and upgrading their infrastructure (Ruby 1.9+encodings) so tackling one of the hard problems (release stats, bug tracking stats) is just out of scope for the foreseeable future)

Felix Schwarz over 9 years ago