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.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]
suggestion how ohloh could get a LOT more information
Hi,
i'm the author of hamsterdb (http://www.ohloh.net/projects/5316?p=hamsterdb).
currently, i have a problem which you cannot solve so far: a part of my repository now contains a foreign AES library and zlib. I have not written these libraries, but suddenly my LOC-count jumps up by 10000 lines and all the statistics are flawed - and i don't want to adorn myself with borrowed plumes.
so here's a suggestion how this and other features could be implemented.
similar to a robots.txt file for webpages and search engines, we (authors/maintainers) add a ohloh.xml file to our repository.
this file has allow/disallow-rules (that way we could remove autoconf-files and 3rdparty-files from the loccount).
and you could even add many other elements to the xml file, i.e. the number of unit tests, the supported platforms/compilers, which licenses are used, etc etc.
that way, you could get a lot of information which you can't get through source code metrics.
regards
chris
Hi Christoph,
This is a fine idea, and one we've knocked around a few times before. It keeps getting delayed for various reasons, but we have wanted to implement a robots.txt-style feature for a while.
Another idea we've had is to automatically recognize duplicate code between projects. If Ohloh has prepared a report for AES library and zlib, then it's not difficult for us to recognize identical files between your project and the others, and presume that you are including them as libraries. This has some design challenges behind it, but the trick of detecting identical files is pretty simple for us.
