Improve description of when to use patches and update CVS account creation page

I made some edits to the patches page. Please review and supply further changes. Thanks.

Change of wording for CVS account page. Should be inserted above the form. Form should be changed as follows:

• Remove bug fix option -- we don't seem to approve for bug fixes, that is what patches are for.
• Radio buttons for new translator, new module/theme, or co-maintainer
• Gnu GPL should be a checkmark, and be required

Patches are the primary way to submit changes to existing core code or contributed modules, and CVS accounts are not required to submit patches. CVS access to the core and contrib repositories is available to all users on an anonymous basis. A CVS account is only required and generally only approved for one of the following reasons:

1. You want to be the main translator for a new language. Additional translators may supply patches.
2. You want to contribute a brand new module or theme to Drupal. If there are existing module(s) with similar or overlapping functionality, you will be encouraged to submit patches to those projects instead. having a working example of such a new module is often useful.
3. You want to co-mantain an existing module. Patches can be used for this as well, but there are a few cases where more than one developer will want to work together directly on larger, more complex modules.

If you are interested in the status of your application and/or have been rejected and would like to discuss further, please use the contact form to get in touch. Please note: due to high demand, it may take as much as 1 week to have your CVS account approved or denied.

eldarin: please start a new forum post or issue -- this task is for improving the description of using patches (already updated at http://drupal.org/node/22568 -- please edit and include further changes if needed) as well as improving the wording/feedback on the CVS account page.