Forums : Posts

We do plan to add support for more source control systems as development resources allow, hopefully in the next few months. Which systems we add first will be determined by popular request. Thanks for the input!

Hi dirty, I posted about this same subject in another thread.

Thanks :-)

Hi Patrick, Thanks for finding this, and for giving me a good example. It's very helpful. We've been suffering from some database troubles lately, and I think this problem arose when we had to ... [More] restore a database backup and some of the recent edit history got jumbled. I agree, the database should prevent this from happening. I'm actually a bit surprised that it does not. I believe this was a one-time issue related to our database restore. I've cleaned up the existing duplicates, and will investigate why the dupes are not being caught by the database. Thanks, Robin [Less]

As of KDE enlistments the download of the source code of KDE has been paused, can I have more info on this ? If several enlistments should be created, please, let me know.

Hi Etaew, Your problem is more common than you might think. I have seen several other projects which attribute code to other authors in their comments. We are currently trying to solve the general ... [More] problem of a person who used two or more different names within a single project, or a person who worked on several separate projects. We'd like to be able to attribute all of this work to a single real person. By putting a mapping layer between commit logs and actual people, we open up the possibility do what you are proposing, which is to extract an author name from the commit comments based on some kind of pattern recognition. It's relatively simple in theory but the trick is achieving this at massive scales. I must admit this is probably going to take a while to achieve. I reviewed the Subversion log for Dawn of Light, and I wanted to point out a complicating factor: It seems that a single commit often includes attributions to several different developers. This means that it will be impossible from the source control to figure out who wrote what code -- we can only pull out a single diff from Subversion, but with multiple names attached to that diff we don't know where to attribute the changes. To implement your feature request, at a minimum, you would need to be sure to attribute all code in a commit to a single person. If you really like the model of random patches contributed to official reviewers who do the actual commit, I'd recommend you take a look at Git. Git is used by the Linux kernel team to support exactly this development process. When people around the world send you a patch for your project, as an administrator you can review or amend that patch, but Git will retain the original authorship information in the log. Finally, regarding the validation problems you are having with tags, I'll take a look at this right now. It sounds like a very simple oversight in some recently added code. I really appreciate the feedback. Thanks for coming to Ohloh! Robin [Less]

Hi jdpipe, It's unbelievable but true: we don't parse FORTRAN (I love a language properly spelled in ALL CAPS). Equally unbelievable, you're the first person to discover this. We'll definitely add ... [More] support for it -- give us a week or so. Thanks, Robin [Less]

Yes, that was pretty bad, especially considering how easy it was to fix. Thanks for pointing this out. It's much better now.

Thanks for the prompt attention Robin, it looks as if things are on track as far as I can see. Your parser seems to correctly recognize the code. Thanks again, Jeremiah

ogourmet, There is nothing that prevents you or anyone else from adding the Tcl/Java project yourself. Having the ohloh project admins/devs add other people's projects when it's been as open and ... [More] flexibly designed towards community involvement would be a certain waste of their time. If you want the project added, add it. Cheers! [Less]