Forums : Posts

Yes, we are considering two approaches to this problem. First, we have had a lot of recommendations to create a robots.txt-style file which would contain instructions for our source code crawler. ... [More] From this file, you could attach labels to directories and files, or exclude certain directories and files from the Ohloh report. This is simple enough in theory, yet complicated in practice. It does seem reasonable we could get this done once the functional questions are all answered. Second, we already have all the source code for Prototype in our system. There's no theoretical reason that our system couldn't realize that some of your source code is not original to your project, and could mark it as such. In this way, Ohloh could automatically discover relationships between projects based on duplicate code. This will take a bit of number-crunching power and a lot of development work, so it might be pretty far off. [Less]

Well, it's always busy around here ... :-) I would have expected these projects to be updated by now. I couldn't find any particular reason why not. -- there doesn't appear to be anything obviously ... [More] out of place. In any case, I've manually scheduled them for an update, which should run sometime today. Let me know if you need anything else, Robin [Less]

Probably not. The main problem is that when code gets moved from /trunk/a to /trunk/b, from a naive perspective directory /trunk/a no longer exists. You can't add /trunk/a to Ohloh, because Subversion ... [More] will (correctly) complain that this URL does not exist! Yes, the old history is still in the Subversion database, and we could pry it out if we went about things properly. But we didn't plan for this case, so we don't go about it properly. In the long run, it is our intention to download the entire repository with all branches and tags, and to just do the right thing when building our reports. In the short run, we had to start somewhere, and allowing only a single trunk with no branching was an immense simplification for our first design. Eventually we plan to go back and improve this ... but eventually has turned out to be longer than we originally expected. [Less]

Lovely! Thanks a lot for a fast and helpful response.

Our official statement is that we have every intention of opening up our source, it's just taking us longer than we planned to do so. At the beginning we weren't sure exactly what Ohloh was going to ... [More] be. There was a time when the idea of building charts and reports from source control repositories didn't equate to building a website directory of open source software. It also wasn't exactly clear how we were going to pay the rent. Keeping the code closed just seemed like a prudent business move. It gave us options. We knew we could always open up the source once the business plan allowed it, but it would be much harder (or impossible) to do the reverse. So we started out closed. If we had it all to do over again, yes, I wish we'd been open source from day one. It's now clear that our business might actually be better off if we open up. But here we are, and it's going to take a little work on our part to get the code out there. And we're dreadfully busy, so this task keeps taking a back seat to more pressing issues. Opening up our code is my favorite to-do item on our white board. [Less]

In add project page, sort license menu by popularity, so the more common licenses are at the top and easier to select.

DARCS support Registration authentication via XMPP (Jabber isn't as broken as greylisting, I feel like my confirmation mail is being held back forever)

This is an extension to http://www.ohloh.net/forums/3491/topics/983 If you want to include 2d-vector art as code, you should count svg files. The problem is, that they are not hand-written mostly ... [More] and thus not very representative of the work involved. The easy to implement thing is, that svgs are simply xml files. [Less]

Being able to ignore /lib/ would make my project stats much more accurate; currently around 50% of the LOC is third party...

If you do that, the total amount of code lines would be much bigger because lots of them would be duplicated. If you want to control more branches you could create more proyects. This way you could ... [More] control the trunk from the Drupal proyect and the branches from Drupal 5 or Drupal 6. [Less]