I'm a bit confused by the layout of the redesign_modules_sandbox.
I dig the stagingX/ folders for each staging server, and, the 'stagingX/custom' folder seems to me to be obviously new custom-made modules. However, could someone elaborate on the difference between the contrib folder and the patched folder? I didn't see any details on how to do this in the new code repository wiki page.
Specifically the section in the wiki page that I'd like to elaborate on is:
"if you're throwing the latest version of views in on staging5, put it in staging5/contrib/views."
In my case though, I not only want to throw the latest version of drupalorg on the server, but also want to contribute to the drupalorg module. Would that then go into stagingX/patched/ or stagingX/contrib/ ? It seems to make sense to me then to put it into "patched" but I'm not totally sure on that. Also, I see that others have put drupalorg module in the staging9/patched folder, I guess I should follow suit on staging2?
The second question then, is how to get the code in there. I was thinking of doing a branch (svn copy) from one of the existing places where drupalorg module exists in the repository, but dont know which "place" has the most current, or 'best' version to branch from.
Is https://svn.drupal.org/drupal/vendor/drupalorg/ "synced" with cvs? If so, I think the recommended way would be to do something like this:
svn cp https://svn.drupal.org/drupal/vendor/drupalorg https://svn.drupal.org/drupal/redesign_modules_sandbox/staging*/patched/drupalorgAnyone feel free to contribute, thanks.
James

Comments
"Patched" is for modules that have a patch applied, not custom
So here's my general strategy:
"Custom" is for modules custom to this site.
"Contrib" is for modules straight out of the contrib repository (in other words, they could be updated to the latest contrib version without losing anything)
"Patched" is for modules to which we've applied a custom patch. We have to be careful with updates, to apply the patch again.
When a patch is accepted and goes into CVS, then the module can be moved out of patched and into contrib.
answerd my own question
if you're gonna copy drupalorg module. dont copy from vendor folder.... copy from redesign branch.
svn cp https://svn.drupal.org/drupal/drupal.org/redesign/sites/all/modules/drup... \https://svn.drupal.org/drupal/redesign_modules_sandbox/stagingX/patched/...
-m "branched drupalorg module from redesign to stagingX sandbox"
@rfay, you could update the wiki with this snippet if you think is useful.
Drupalorg is in some trouble right now anyway
Drupalorg will actually be coming shortly from a patched version in CVS - see
http://drupal.org/node/665976
and
http://drupal.org/node/666590