Forums : Suggestions for Ohloh 2.0

In https://www.ohloh.net/p/libguestfs a lot of code is generated code, so ohloh is totally off-base about this project, for example claiming that the code has too few comments, and that it is mostly written in C.

We commit generated code into the repository to make it simpler for developers to build, since the generator is somewhat esoteric.

Anyhow I think you should look at files that have a warning at the top. For example if warning generated do not edit (etc) appears in the first few lines of a file, either discount that file or give it less weight.

rwmjones almost 16 years ago

I think this is a pretty interesting idea. If someone wanted to extend Ohcount to recognize generated code, that would be a really cool addition. It would make sense to have Ohloh ignore generated code by default.

Another option we have considered in the past is some kind of robots.txt-like functionality, allowing users to tag certain filepaths to be ignored. We could also use this functionality to tag code as documentation, test code, etc.

Robin Luckey almost 16 years ago

Rather then a robots.txt like functionality why not allow for the addition of ignore rules in the enlistments section. This way a repository doesn't have to be changed to make Ohloh count the code correctly.

Andrew Fenn almost 16 years ago

I'm all for the ignore rules. In one of my projects, 99% of the code and markup was foreign code, making the code analysis completely irrelevant. I changed that recently and removed the foreign code from the repository, but then the lines of code graph is still totally useless since the lines of code count was so high that the current amount of code is not even visible on the graph (see https://www.ohloh.net/p/tagaini-jisho/analyses/latest )

Alexandre Courbot almost 16 years ago

I have added a ticket: http://labs.ohloh.net/ohcount/ticket/317; unfortunately I am not a Ruby coder (yet); anyone else up for it?

tpokorra almost 16 years ago