[drupal-docs] [task] Improve description of when to use patches

[eldarin]

Issue status update for 
http://drupal.org/node/30461
Post a follow up: 
http://drupal.org/project/comments/add/30461

 Project:      Documentation
 Version:      <none>
 Component:    Developer Guide
 Category:     tasks
 Priority:     critical
 Assigned to:  Boris Mann
 Reported by:  Boris Mann
 Updated by:   eldarin
 Status:       patch (code needs review)

How will copyrights be maintained ?




eldarin



Previous comments:
------------------------------------------------------------------------

Mon, 05 Sep 2005 20:49:05 +0000 : Boris Mann

CVS account approvals are having all sorts of problems because it is not
well documented that patches are one of the core ways to include code in
the Drupal core and contrib.


The top of the patches page (http://drupal.org/node/22568) needs to be
re-written to describe how/when to use patches to contribute to code
development.




------------------------------------------------------------------------

Mon, 05 Sep 2005 21:09:45 +0000 : Boris Mann

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




------------------------------------------------------------------------

Mon, 05 Sep 2005 21:32:32 +0000 : Boris Mann

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 [1] 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 [2] 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:



* You want to be the main translator for a new language. Additional
translators may supply patches.
* 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.
* 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 [3] 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.


[1] http://drupal.org/node/22568
[2] http://drupal.org/node/22288
[3] http://drupal.org/contact