Thanks!

It looks like the Launchpad code import finished today, but the line counts look a bit fishy: https://www.ohloh.net/p/launchpad/analyses/latest In particular, -3,291 lines of SQL and -2,406 lines of ... [More] HTML. Not sure how those numbers would get into the stats. [Less]

At the moment if a project uses an unsupported VCS, the best option currently is to select Ohloh doesn't support this project's source control system (e.g. Mercurial, Darcs, etc.). Some problems with ... [More] this include: Ohloh has no idea what system the project does use. So it has no way to gauge the popularity of individual unsupported systems. If Ohloh does add support for a new VCS, users will have to go through filling in the enlistments. If users could provide URIs now, there would be a bunch of branches to scan immediately. I can get information about VCS location for projects using a supported VCS directly from the Ohloh site. This would be useful information for other projects even if the branch contents are not yet being scanned. [Less]

Looks like you're missing a few things. after creating the OAuthRequest for the /oauth/request URL and signing it, you need to make a request to that URL. This would be a POST request to ... [More] http://www.ohloh.net/oauth/request_token with oauthrequest.topostdata() as the body. The response would give you a request token. Using the request token, you need to authorise the token. This requires opening a web browser at http://www.ohloh.net/oauth/authorize?oauth_token=XXXX (the request token you got in the previous step). Once you've authorised the token, make a request to the .../access_token URL, passing in the request token. This is done in almost the same way as in (1). When you do this request, you'll exchange the request token for an access token that you can use to access the API. The Python oauth library isn't that great, so it is pretty easy to make mistakes like this :( [Less]

Isn't ActionScript just a variant of JavaScript? Does it make sense to treat it differently?

Looking at the CVSROOT/modules file, it looks like they pull together a bunch of dependencies to create the source tree. Checking out src/gdb from the same CVS root is probably a good indication of ... [More] the code that is unique to GDB, and doesn't get mangled by any CVSROOT/modules lines. [Less]

If a project does not use one of CVS, Subversion or GIT, the only option available is Ohloh doesn't support this project's source control system (eg: Mercurial, Darcs, etc...). In cases like this, I ... [More] think it would be useful to store the type of VCS that is used, and possibly a URI to a public repository. This would help identify which unsupported systems are widely used (or used by important projects), which could help in deciding what is worth putting effort into. Also, storing the public repository URIs would allow automatic enlistment after support has been added for a new VCS. [Less]