summaryrefslogtreecommitdiff
path: root/docs/internals/contributing/bugs-and-features.txt
diff options
context:
space:
mode:
authorAymeric Augustin <aymeric.augustin@m4x.org>2012-06-07 18:48:29 +0200
committerAymeric Augustin <aymeric.augustin@m4x.org>2012-06-07 18:54:43 +0200
commit90fb6a46485d4f3c70d3864ab0a0e2f619449d31 (patch)
treee9385c8956eca6d813763582e78da6c4f96f995e /docs/internals/contributing/bugs-and-features.txt
parent1a412dda621d8623abb91f8687f52de30a79901a (diff)
Fixed #18436 -- Updated contributing docs for git.
Most of the credit for this large patch goes to Anssi Kääriäinen. Many thanks to all the people who contributed to the discussion.
Diffstat (limited to 'docs/internals/contributing/bugs-and-features.txt')
-rw-r--r--docs/internals/contributing/bugs-and-features.txt5
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/internals/contributing/bugs-and-features.txt b/docs/internals/contributing/bugs-and-features.txt
index 9492cde0ab..76a2bd2374 100644
--- a/docs/internals/contributing/bugs-and-features.txt
+++ b/docs/internals/contributing/bugs-and-features.txt
@@ -149,9 +149,8 @@ description.
As with most open-source projects, code talks. If you are willing to write the
code for the feature yourself or, even better, if you've already written it,
-it's much more likely to be accepted. If it's a large feature that might need
-multiple developers, we're always happy to give you an experimental branch in
-our repository; see the :doc:`writing-code/branch-policy`.
+it's much more likely to be accepted. Just fork Django on GitHub, create a
+feature branch, and show us your work!
See also: :ref:`documenting-new-features`.