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
info@openhub.net
Filtering source repository dirs/files
Hi,
in our project we have a number of files that are actually automatically generated and not hand-coded; also, these files are rather large and probably skew the statistics. Thus, to get a more accurate representation of what the human contributors created, it would be nice to have the ability to exclude file and/or directory patterns from the collection of statistics.
-f.r.
Greetings,
you just need to add a robots.txt like this
http://ayam.cvs.sourceforge.net/ayam/ayam/robots.txt?revision=1.1&view=markup
to your repository.
best regards,
Randolf
This is not true!
Ohloh does not respect a robots.txt file in your repository. This is a feature that has been requested by many Ohloh users, but it has not been implemented. It may apply to some other crawlers, but Ohloh will ignore it.
Then good I didn't rush to make one ;)
Oopsa; I stand corrected. Thanks, Robin, for clearing this up. I just wonder, why the statistics for my project (Ayam) seem to be correct. *scratches head*
best regards,
Randolf
Greetings,
I noticed a similar problem, and just deleted the enlistment and re-added it pointing directly to the src/ directory under trunk/ instead, so it doesn't pick up all the configuration and extra crud. (For example, I include JRuby and its libraries in the project, so it thought my app was 76% Ruby, when it's currently 99% Java, with just a smidge of Ruby.)
-- Morgan
This really only works when you have all your relevant
source files in one single subdirectory. I can assure you not every project is structured that way.
Greetings,
I didn't claim it was an answer for everyone, I just thought it would help some.
It turns out it does work, although there was some weirdness. I had to go in and disable the 'best_analysis_id', and then I saw that it hadn't finished integrating the new info, and once the new best_analysis_id was generated, it had the correct info.
I believe you could create multiple enlistments, pointing to the relevant directories in your project. It's a whitelisting approach instead of a blacklisting approach, which might help more projects.
Again, no claims it'll work for everyone, or your case in particular. I fully agree, it'd be really nice if we could configure what is seen by ohloh.
-- Morgan