Usage policy
The following is quoted, in part, from the contributions/README.txt file in the Drupal CVS repository.
Jump to:
General
This is a free service provided by the Drupal developers for the Drupal community. By using the repository you agree to the terms of use (see the TERMS.txt file).
All code must be licensed under GNU/GPL. If there is a problem with this, contact the repository administrators.
Always make sure there isn't already contributed code that does the same thing as your code. Instead, contact the maintainer of the other project and try to merge the projects into one.
Do not branch Drupal core modules/themes; instead, make patches against core and submit those for review. In case a patch is not approved, or very unlikely to be approved, contact the administrators of the contributions repository for advice.
DO NOT include code from a non-Drupal project in the repository. If your module requires non-Drupal code, provide a link to where the other code can be downloaded and instructions on how to install it.
File locations
docs/
Example implementations of Drupal features, logos, marketing material.
modules/
Contributed modules. Development versions go into HEAD, not to a sandbox.
profiles/
Contributed installation profiles. At this time, only files ending in .profile or .txt are allowed to be committed, since installation profile maintainers should *NOT* include the code of the modules that are enabled by their profiles.
theme-engines/
Engines which are used by one or more of the contributed themes.
themes/
Contributed themes. Development versions go into HEAD, not to a sandbox.
Alternate styles for an existing theme should be submitted as subdirectories of the existing theme's directory in this manner: themes/main_theme/new_style.
theme-styles/
Use of this folder is deprecated.
translations/
Gettext Portable Object-based Drupal interface translations.
sandbox/
Contains code that modifies the Drupal core in such a way that it makes little sense for the code to reside in a standalone patch in a project. Any code that fits in a standalone module should go in modules/.
All sandboxes should include a README.txt file that explains what changes are available and the state of the code. The key is to have enough documentation so people who review the code don't spend hours doing it, and code clean enough that it can be committed without too many changes.All code should comply to the coding standards. Any patch that fails to do this will generally be treated as unfinished work and ignored.
Sandbox Guidelines
The sandbox is for use by Drupal developers with CVS access. It can be used to collaborate or share code that is related to the Drupal project -- whether it is core or contributed modules. Inappropriate uses of the sandbox include storing "personal code" -- for example, don't store your website in your sandbox.