I'm trying to add this repository:
To the "WordPress Plugins" project. I get a server error every time, possibly because the repository is fairly large. It's roughly equivalent to the contributions repository for Drupal.
I can't recall why, but our code is instructed to specifically forbid root directory enlistments like this one. Also curiously, our website decided to explode instead of simply give an URL validation warning.
I've posted a fix to this, so you should be able to enlist this repository now.
If it's as big as you claim, it might not go down easily. I'll keep an eye on it and give a kick start if and when the download gets interrupted.
I've enlisted the repository for WordPress plugins now and it has accepted the url ok.
Now we just have to wait for the downloaders to choke on the size ;-)
So far so good. I'm estimating it will take us about a week to get the whole lot.
It looks like it's going backwards!
It has started downloading again but it is back down at revision 137 - I'm sure the first time it had reached over 1000 revisions.
Or am I reading the data incorrectly?
Those numbers aren't hard Subversion revision numbers.
The first number is the number of revisions downloaded since the job started running, so it always begins at 0, regardless of the actual Subversion revisions numbers.
The second number is the count of revisions yet to be downloaded by Ohloh when the job started. This number should be smaller each time the job restarts, to reflect the forward progress we made last time we ran the job.
Downloads are incremental, and don't start over from scratch unless we force them.
Was just a little confused. But that makes perfect sense.
The import seems to have got stuck.
It now says: "No job is scheduled."
I killed the job manually, after it progressed only a few percent towards completion after running for two weeks. At that pace, we'll be downloading it for a year. The checkouts are simply too slow.
If the server supports it, we can try using svnsync to create a local mirror. I'll investigate this option, although the size of the repository is going to create other complications beyond simple download time.
We'll have much better success creating small projects that target particular plugins, which I think also better matches the spirit of Ohloh. If all of the plugins are lumped into a single massive report, it will be impossible to investigate and compare the individual plugins with Ohloh.
I think quite a few of the plugins may already have projects here on ohloh.
I ran an svnsync locally from the repository which does work - however it took about 1 day to sync the whole repo and used about 5G of disk space!
I guess individual projects are probably better as that way Ohloh can be restricted to just pulling in trunk.
Or we could enlist each plugins trunk folder under one project - does Ohloh reuse checkouts if they are enlisted in more than one project?
Yes, if two projects share the same source control URL, Ohloh will reuse the same data for both projects.
Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.