Forums : Technical Issue Help
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]
Removed enlistment, summary stays
Can you please fix this for project 5907. It's just so annoying to see nonsense like decreasing development activity
etc there, just because ohloh's measurement approach is so horribly broken and cannot work on a complete repository. Sorry for being bitter, but this hurts projects. Especially with your comparison feature. Before you do that, you really should get a proper foundation done that allows fair comparisons. That includes giving the option to exclude certain paths from the metrics (say, generated XML data or vendor libraries or whatever).
Would that be possible, please? I'd really much rather have no statistics than completely wrong statistics. Thanks.
I'd be happy to do this. One affect of removing the report is that contributors to the project will lose their code experience and implied kudos (received from being contributors to a project that's been stacked).
Go ahead and remove?
The coding experience does not worry me, but the kudos... hm. I have fewer kudos than the project has stacks, though. How does that work exactly? And isn't that stuff added again when I add enlistements back in?
Your Kudo rank is based on kudos received from people directly. Contributions to stacked projects also act as a kudo, but it's a kudo to all the contributors, shared proportionally by commits. In the case of Agavi, you're receiving a significant portion of an additional 28 kudos. In both cases, kudos from people with higher kudo rank count more.
You're right - adding the enlistment back would restore the kudo rank.
Okay, then I think it's fine if you go ahead and remove the report. I just hope nobody else adds an enlistement soon afterwards or I need to bother you guys again. Any idea when a new system for this is implemented? I once proposed that activity is measured using an entire repos (or parts of it), and then one would add a separate, dedicated repository path just for the code metrics.