Forum Posts

Ahh, got it, thanks a lot for your help, now I figure out, but seems that we experiment problems modifying SVN source.... there is listed https://www.mambo-foundation.org/svn/mambo/trunk but since ... [More] the project is handled in branches, and we don't merge the changes to the trunk the I think that the right path should be https://mambo-foundation.org/svn/mambo what do you think? [Less]

sorry just found the answer in the forums "not supported yet might in the future" I would add a big +1 for this functionality Also I did search but obviously not well enough :(

Hello, Is there any way to exclude code from the analysis ohloh undertakes? We have a large amount of C++ code which is auto generated by a tool and while we store in the svn structure strictly it ... [More] should not be being counted in stats analysis. The nature of the auto generated code (no comments etc) is also causing havoc with the overall representation of the project. Any help greatly appreciated. [Less]

Hi Ingo, Thanks for pinging us. Looks like we had an intermittent network failure and we stopped downloading updates. I kicked it off manually and it crawled successfully. It should show a fresh report in a few minutes. Sorry for the delay... -jay

Yes, the code is the better documentation to understand what it does. But on the other hand nobody never said that comments were not helping to understand faster and easier. By experience i can tell ... [More] that a well commented source will be easier to maintain. A bad or non commented code will likely become crappy. Christoph Rupp is true, there's a lot of good code with comments but there is also a lot of bad code with comments (and often it's bad code with short and completely useless comments). [Less]

Hello, we are just wondering if something went wrong for the project http://www.ohloh.net/projects/5510/ For the enlistment "yale" (the core of the application), the download process was started ... [More] several weeks ago and stopped since then with the message: "Step 2 of 3: Importing source code into database (Paused)" Would be great if you could check if there was an error or something since the first time the project was analyzed everything went fine. Thanks for your service in general and for your help in this matter. Cheers, Ingo [Less]

Right ... two minor details that would be nice to have fixed... Firstly, the feed (I'm pulling the rss one) doesn't appear to have the actual project stated, or if it does, my akregator doesn't seem ... [More] to show it. Could it be prepended to the subject maybe? Secondly, said feed also doesn't seem to show the number of stars the review has. Perhaps throw that at the begining of the review body? Or at the end? As I say, it's quite possible the feed, or the atom one I don't pull, do contain the info and my client doesn't show it ....? [Less]

After careful thought, I'm agreeing with the more comments better camp. There are some prime examples of code where more comments is a sign of cluelessness "/ Not really sure what this does, but ... [More] everyone else has it /"-esk stuff. On the other hand, there is a patch of ground between good code and inspired code where the code is nicely succinct, effective but takes 10 minutes of hard thought to remember exactly how it works. Code that works well and looks nice, but lacks the self-documenting quality that pushes it in toward the inspired area. Sprinkling some well worded comments in the proper places makes such code much nicer to think about ... though overdoing it is worse than not bothering :/ Well commented code (as opposed to code with lots of comments, distinction important) at least demonstrates that the writer understands what their code does, and is happy to help others understand it as well. [Less]

As a developer of a combined application/library, I will completely disagree with the idea of fewer comments being better. I can't expect users of the library to read all the code for the ... [More] implementation of the API; it is important that there is a relatively high comment to code ratio because the comments describe how to use individual functions/methods, not merely how the functions/methods are implemented. [Less]

Interesting thread. When I use an application, I really don't care much about the comment ratio of its source code. After all, there are many examples of insanely great developers who subscribe to ... [More] "the code is the best form of documentation". However, I do care about comments when I think I might have to maintain/fix/enhance the code myself. Just a few short lines explaining the reasoning behind the design can save a lot of time and frustration. [Less]