Forums : Feedback Forum
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]
genshi2js statistics
I've got two issues with the generated statistics.
A chunk of javascript (MochiKit.js) is recognized as some 73% of the project, while this actually is nothing more then a data file from the perspective of my software.
MochiKit.js is attested a very poor source comment rate (unsurprising as it's compiled to a stripped version from more verbose source). The python source has quite a few comments, but since it's shadowed by the amount of javascript code, it does not seem to matter for the overall statistics.
Well, also it gives a wrong picture of the project since the whole of MochiKit.js isn't anything I needed to write, it's an inclusion there for convinience.
I conclude it would be prudent to have a way to exclude files/directories from the statistics (i.e. mark them as data or whatever).
On a sidenote, this would leave me with some 3 months of work for the python stuff. But the actual efford gone into that for me is more like 2-3 weeks. I find the LOC time estimation are far off reality (at least for me).
HI doc,
The ability to ignore sections of the source code is something that a lot of people are asking for, and it's high on our list of planned features. It's very common for projects to include library code from somewhere else, and it's usually correct to exclude that code from the project report. I can't guarantee a timeline, but this is definitely something we plan to do.
I agree that the project cost estimator is usually far too high for small open source projects. We have borrowed the simple COCOMO model, which is an old, established estimating tool that comes from the world of large, bureaucratic software processes. It assumes that you have planners, testers, writers, and a deep management tree, which is something that very few open source projects have. Also, it is most accurate for large projects with a long history, and for a project as small and new as genshi2js, it's probably wildly inaccurate.
From reading the source control logs, Ohloh can make a relatively accurate measurement of the real time put in by the developers. For example, we've estimated your contribution at 2 real months. This is much more accurate than the COCOMO estimate -- but this method of estimating can't account for work that doesn't directly touch the source code, such as planning and support. In any case, we might offer an alternate calculator in the future that can be driven by actual source code activity instead of the COCOMO estimate.
Thanks for your feedback -- it's very valuable to us as we plan future features.
Robin
