Hi bermi, There was a weakness in our source code parser which caused it to falsely detect your "Lesser GPL" citation as a full GPL citation. I've tweaked our parser to correctly identify this as ... [More] LGPL. I will schedule an update to the Akelos report page, so you should see the improved results with 24 hours. The GPL conflict warnings should go away. Regarding the composition of both BSD and LGPL into a single license, this is just too complex for our parser to understand. As our system works today, these files will be licensed as both BSD and LGPL simultaneously, but it will not have the understanding that BSD has priority in the case of conflicts. In the near future, we hope to offer the ability to drill into the license report to see which files cite which licenses, and to actually view the license text online. Hopefully, this will reduce confusion over licenses. Robin [Less]

This is an issue that several projects have brought up, and the answer is no, at least for now. There is a more general version of this feature, in which the same person might be contributing code to ... [More] two or more separate projects, and we'd like to aggregate that person's work accross all projects. This is something that we've been discussing for a while, and it is definitely in our plans for the future, but I can't promise when we'll have the resources to make this happen. [Less]

Hi entel, Thanks for reporting this. It was a bug in our code: if you added an RSS feed to a project and then deleted that feed, you could not add the same feed again. I fixed the problem and I added the RSS feed back to ejabberd. Thanks, Robin

Hi Elpie, "There is still confusion around as to where the project resides." Ohloh attempts to automate the software audit process. We believe that source control history is a powerful ... [More] indicator of a project's health. Confusion around the project history reflects poorly on any audit, whether automated or manual. We used the repository indicated at SourceForge to create our report. This repository is less than two years old, has not seen any activity since May of 2006. If there are other repositories we should be using which reflects either older or more recent activity, please send us a link and we'll be happy to update our report. Robin [Less]

Hi djd, It looks like Derby was the victim of a database crash we had at the end of December. I've started a fresh import of the code, and the new report should be ready today. Thanks for finding this, Robin

Hi sean, Thanks for your very interesting feedback. It's nice to get very detailed "bug reports". You have a ton of cool ideas and links in this post, so I want to spend some time thinking about ... [More] them before I comment, but in the short term I want to address the years of contribution issue. I think the key here may simply be that it's not obvious what we mean by "7 years contribution", and our terminology is inconsitent on different pages. Our source control analysis does indeed stretch back the full 23 years to December of 1983, which you can see on the commits listing. Incidentally, I think you may hold the record for longest continuous history on our system -- I'll have to check. The reason we say that mike has only 7.0 years of contribution is because we count only months in which mike actually checked in code. If you look at mike's timeline, you can see that before 1995 he was only checking in code during one or two months out of the year. In total, he checked in code during 84 different months, for 7.0 total years. Very soon, we plan to expand our developer analysis to include factoids such as "Joined the team in 1983" and "Retired from the team in 2000" which might clear up some confusion, and I concede that we should be much more clear about what we mean when we say "7.0 years contribution". I'll study the rest of your post in detail and get back to you again. Thanks again for the great feedback, Robin [Less]

Lawouach, I accepted your certificate on our server farm, and the source code is now downloading. viyyer, I accepted the certificate for https://svn.bitflux.ch, and that repository is now ... [More] downloading. However, http://flux-cms.org has some other problem. When I try to connect to the server, I get the following error: $ svn info http://flux-cms.org/Installationof_FluxCMS svn: PROPFIND request failed on '/Installationof_FluxCMS' svn: PROPFIND of '/Installationof_FluxCMS': 200 OK (http://flux-cms.org) Do you know what might be going on with this server? Robin BTW, our wiki markup processing turns underscores into italics, so the urls look a little funny, but I believe I've used the correct urls. [Less]

Hi jdpipe, We've skipped the revisions, and it looks like the download is working again. You'll see a single checkin from a developer named "ohloh" which includes all the changes for the skipped revisions. Thanks, Robin

Hi jdpipe, Yes, I saw this error over the weekend. It looks like it may have been caused by a temporary network failure or a Subversion timeout. I've rescheduled the job and I expect it to finish today. Thanks, Robin

Hi pixelbeat, I took a look through our analysis for this project. It looks like we simply don't recognize the language this project is written in. Off the top of my head, I don't even know what ... [More] language the "*.po" file extension is used for -- which goes a long way toward explaining why our system doesn't know. :-) Our system is also very dependent on file extensions for language identification, and it gets pretty lost when a file doesn't have any extension at all. In your case, this means we are not recognizing very many of your bash scripts. This is an issue that a lot of people are pushing us to fix. Thanks, Robin [Less]