Hi welterde, Sorry it has taken so long to respond. It looks like we lost some data in this project. I started a fresh report for pygments to clean up the problem. The new report should be ready within an hour or two. Thanks, Robin

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 LGPL. ... [More] 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 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 mokhov, Sorry it's taken so long to reply, but you raised a lot of good questions and I felt you deserved a thoughtful response. Internally, we actually do split languages into two broad ... [More] categories: markup and procedural. Currently, we consider XML, HTML, and CSS as markup languages, and everything else is procedural. We currently only recognize about two dozen languages, so this list may grow. We originally did this because we wanted to identify the primary language of a project, and we discovered that a lot of projects where coming back with HTML or XML as their primary langauge, which was clearly wrong in most cases. Typically, this happened when a project included a lot of web content or documentation. Now we ignore markup when determining the primary language [with some limits: a project that's 99% XML and 1% shell script will still come back as an XML project]. Ironically, the primary language doesn't even get exposed on the current website. However, we can envision a day where you might do a search for projects written only in a particular language. A surprising number of Ohloh users don't like the fact that our reports reveal a lot of HTML or XML in their projects. I'm not sure where this resistance comes from, but it feels like the users would like us to report markup line counts separately from real languages somehow. Personally, I think that in the future we're going to de-emphasize absolute line counts as a metric in favor of frequency of checkins and relative complexity of those checkins. I'm a bit puzzled about what to do in the case of a single developer who writes both a lot of HTML and a lot of C++. Is it more correct to label this person as a C++ developer or an HTML author? With equal output in each langauge, I'm sensing from you that we should call this person a C++ developer. If this person had written no C++ at all, then HTML author is the correct label. Where, then, is the boundary between the two? How much C++ can a person write before we discredit the HTML? I think that the right answer is that we shouldn't try to pick just one label for this industrious person. If we want to give a one-line summary of this person's talents, I think we have to list both the C++ and the HTML, and the fact that one language is procedural and another is markup doesn't even enter the picture. This is a pretty interesting topic for me, so I'd love to hear any more thoughts you have. Over the next few months we're probably going to be developing some deeper analyses for individual developers, so this is a good time to brainstorm. Thanks, Robin [Less]

Hi bradh, As it turns out, this was not a 2007 rollover problem. Unfortunately, we had a database crash over the holiday and we lost a few projects. I've scheduled a fresh, new report for Qt which ... [More] should be ready in a day or two. Until then, I've rolled back to a prior report which we generated before the database problems. Thanks, Robin [Less]

Done. Thanks for coming to Ohloh! Robin

Hi maxslug, Yes, we've been thinking about doing something like this for a while now, almost from the very beginning of Ohloh. It's really just a matter of development resources and design time. This ... [More] is definitely a direction we are going in, so if you have any cool ideas for how this could look please share them! Robin [Less]

Yes, it was an issue with the SSL certificate. Much to our frustration, Subversion can't be instructed to blindly accept a new certificate -- somone has to be there at the console to type in a ... [More] response to Subversion's question. Until Subversion puts in a workaround for this or until we cobble together a custom build of Subversion, we need to manually set these up. I've accepted the certificate on our server farm and the source code is downloading now. Thanks, Robin [Less]