Forums : Feedback Forum
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.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]
duplicate elimination for bundled/copied software
It would be nice if ohloh's enlistment-analysis widget were to stop crediting projects for their reuse/bundling of other packages, when they simply duplicate preexisting commits or modules from projects already known to ohloh. The multiple-counting inflates figures, and in some cases can outweigh the original contributions of the project itself.
Frank,
It's an interesting idea but likely to be hit-or-miss (mostly miss) for us to correlate all the appearances of outside code in all ohloh projects. That is precisely why the ignored Files
feature was added. Before that, project managers had to create a jigsaw puzzle of enlistments, piecing around the external code in their repositories. We do remind them to leave out all the dependencies and enlist only the project's original code but often the advice is ignored. Regardless, I'll pass the suggestion up to management to see if we can find a handy-dandy matching routine to filter out the distractions.
Thanks!
Note that project managers have an incentive to make their projects look more lively rather than less. So, any work you'd ask them to do that would have the effect of reducing their activity/community scores is naturally going to be resisted. (The same applies at the individual contributor level, whose work may be copy/pasted into a dozen forks / derived projects.)
It seems like only an outsider would have a desire to see honest
data - or BlackDuck, in order to be known as a presenter of same.
Frank,
Yep... that's the thinking sometimes but it's so transparent to have twelve different copies of your code (plus everybody else's) in the project and SOMEBODY'S going to notice and drop a dime on you. Subtle is the watchword when you cheat. (No advice to cheaters here, however...)
I've made my pitch to management and hopefully we'll get something out of it.
Thanks!
A variant of this problem are duplicate commits in forked projects. One could try to suppress at least those git commits with identical commit id.
