diff options
Diffstat (limited to 'docs/faq/contributing.txt')
| -rw-r--r-- | docs/faq/contributing.txt | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/faq/contributing.txt b/docs/faq/contributing.txt index cdf2b6c6ca..079a789197 100644 --- a/docs/faq/contributing.txt +++ b/docs/faq/contributing.txt @@ -1,14 +1,15 @@ +====================== FAQ: Contributing code ====================== How can I get started contributing code to Django? --------------------------------------------------- +================================================== Thanks for asking! We've written an entire document devoted to this question. It's titled :doc:`Contributing to Django </internals/contributing/index>`. I submitted a bug fix in the ticket system several weeks ago. Why are you ignoring my patch? --------------------------------------------------------------------------------------------- +============================================================================================ Don't worry: We're not ignoring you! @@ -43,7 +44,7 @@ we'll just close the ticket. So if your ticket is still open, it doesn't mean we're ignoring you; it just means we haven't had time to look at it yet. When and how might I remind the core team of a patch I care about? ------------------------------------------------------------------- +================================================================== A polite, well-timed message to the mailing list is one way to get attention. To determine the right time, you need to keep an eye on the schedule. If you @@ -70,7 +71,7 @@ additional attention -- certainly not the attention that you need in order to get your pet bug addressed. But I've reminded you several times and you keep ignoring my patch! -------------------------------------------------------------------- +=================================================================== Seriously - we're not ignoring you. If your patch stands no chance of inclusion in Django, we'll close the ticket. For all the other tickets, we |