Hi folks,

Version Control API is practically ready to replace cvs.module on drupal.org. The only task that remains (besides making sure there are no bugs) is finishing the migration scripts that pull the data from cvs.module to the various Version Control API module tables. I could set up my own set of CVS repositories and work on that data to test stuff (and maybe I'll be doing that as well) but the original drupal.org database makes for the best test case.

dww suggested that you might be able to set me up with a d.o clone, and I need a database dump for that. Hopefully it'll work out somehow.

Thanks in advance from your slow but steady Version Control API co-maintainer,
Jakob

Comments

damien tournoud’s picture

damien tournoud commented

The current database of d.o is quite large. You probably don't need all of it. Can you describe which tables you need from the dump, and if it is possible to restrict it to some of the node types?

damien tournoud’s picture

damien tournoud commented
Status: Active » Postponed (maintainer needs more info)
dww’s picture

dww
we/he/they
commented
Status: Postponed (maintainer needs more info) » Active

If he only needed the CVS tables, I could make him a dump myself. However, he really wants all of the project* tables. And those depend on {node}, {comments}, and {users}. So, it quickly gets out of hand. That's why I suggested a full d.o redesign clone.

If you wanted to remove forum nodes and comments, that'd help a bit. I guess he doesn't need books, either. But otherwise, he basically needs a full (anonymized) d.o clone...

Thanks!
-Derek

drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Active » Closed (won't fix)

Probably no longer relevant.

Component: Database » Servers