Ahoy, friends!

After Drupal.org moved to git much of the code was moved from cvs to git. However there are sections which are only available in cvs such as sandboxes and the contributions/scripts directory.

The read only access to CVS will go away soon

You can still get access to that old content by following these instructions: CVS: Dealing with legacy CVS 'sandboxes'.

You should only follow the instructions on that page about git if you intend to maintain the code as a new sandbox.

Why remove this?

This access was only kept temporarily so people could get at old code. It is going away because this content is not updated and anyone accessing it will be getting out of date information. It also takes up a non-trivial amount of space (and inodes - how nerdy!) so deleting it will help us to remain on our current servers a bit longer. Yay servers!

But, but, I want to keep it!

Great, then you should export the data you need and put it in your own cvs repository. You can even use rsync to get a copy of the whole repository.

Comments

rfay’s picture

Although it seems impossible, I remember one of the issues around this was that people have automated build processes still dependent on CVS pulls.... Might we want to wait until the anniversary of the git migration, or something clear like that?

greggles’s picture

Yes and no...of course it would be nice to wait for the anniversary, but after discussing it we felt this would be somewhat hard to do.

* It's been a long time since the git migration. People with automated builds have had a long time to move away from this.
* The data in CVS is now ~7 months out of date. I can't imagine that automated builds based on 7 month old data are really valuable (?)
* The disk space issue is a persistent problem. Something has to get deleted to make it go away, ideally something big. If we can do this without affecting too many people then it's a great solution since it lets us avoid doing things like removing dev environments.
* There's talk of providing a tar.gz of the repository which would take less space on d.o so it could be provided. That would be useful for someone who had code that didn't make it through the mgiration. But if someone updates their auto-build script to stop pulling from cvs and instead use the tar.gz then it would be just as easy to update to git.
* people may still be trying to authenticate against cvs using old accounts which could put their d.o account at risk. We should shut off as many plaintext authentication mechanisms as we can (#952578: Fix any references to non https resources, fix redirects to avoid double encoding url parameters for details on ssl).

Something has to give for the disk space issue...this seemed like a reasonable one to go after.

fgm’s picture

The CVS repository also includes the contributions/docs/ directory, which I have not found elsewhere, and which includes some of the marketing docs, like the original .AI files for Drupal leaflets used at events.

Also contributions/docs/developer, although it is unclear whether these are still used by api.d.o. or not.

greggles’s picture

The marketing info can go to http://drupal.org/project/emr - want to take that on?

I'm not sure what else is in contributions/docs but it probably should have a similar home somewhere else.

Indeed api.d.o is no longer based on contributions/docs/developer. I've asked to find where it is managed but am not sure.

sun’s picture

What exactly means "soon"?

Daniel 'sun' Kudwien
makers99

greggles’s picture

No more than a few weeks, as soon as Friday?

sun’s picture

Is there a tool or script that allows to convert a CVS sandbox into a git sandbox including history?

I've been pointed to http://cvs2svn.tigris.org/ but that requires local file access to the CVS repo and doesn't work remotely.

Daniel 'sun' Kudwien
makers99

greggles’s picture

In the original article:

You can still get access to that old content by following these instructions: CVS: Dealing with legacy CVS 'sandboxes'.

You should only follow the instructions on that page about git if you intend to maintain the code as a new sandbox.