From 862ade3409ceaa8ec5305e6f5aa26ee0e553cf02 Mon Sep 17 00:00:00 2001 From: Jacob Walls Date: Thu, 20 Aug 2026 18:14:57 -0400 Subject: [PATCH] De-emphasized typo fixes in contributing docs. As part of adding useful friction in front of unwanted agentic contributions, all new contributors are being nudged to have tickets for their PRs. Update the contribution docs with this current practice. Co-authored-by: nessita <124304+nessita@users.noreply.github.com> --- docs/internals/contributing/new-contributors.txt | 9 +++++---- .../contributing/writing-code/submitting-patches.txt | 9 ++++++--- 2 files changed, 11 insertions(+), 7 deletions(-) diff --git a/docs/internals/contributing/new-contributors.txt b/docs/internals/contributing/new-contributors.txt index bf80dee36589..f4462e803a9f 100644 --- a/docs/internals/contributing/new-contributors.txt +++ b/docs/internals/contributing/new-contributors.txt @@ -52,10 +52,11 @@ expected. Updating a patch is both useful and important! See more on Write some documentation ------------------------ -Django's documentation is great but it can always be improved. Did you find a -typo? Do you think that something should be clarified? Go ahead and suggest a -documentation patch! See also the guide on -:doc:`/internals/contributing/writing-documentation`. +Django's documentation is extensive, but it can always be improved. Changes +that materially improve its correctness, clarity, or completeness are welcome. +A minor rewording or pure typo fix is generally not suitable as a standalone +contribution, but may be included as part of a more substantial patch. See +also the guide on :doc:`/internals/contributing/writing-documentation`. .. note:: diff --git a/docs/internals/contributing/writing-code/submitting-patches.txt b/docs/internals/contributing/writing-code/submitting-patches.txt index f3c128716aa4..4feaf05bfbe2 100644 --- a/docs/internals/contributing/writing-code/submitting-patches.txt +++ b/docs/internals/contributing/writing-code/submitting-patches.txt @@ -11,9 +11,12 @@ without a solution. Typo fixes and trivial documentation changes ============================================ -If you are fixing a really trivial issue, for example changing a word in the -documentation, the preferred way to provide the patch is using GitHub pull -requests without a Trac ticket. +If you've contributed to Django before and just want to fix a really trivial +issue, for example changing a word in the documentation, the preferred way to +provide the patch is using GitHub pull requests without a Trac ticket. If you +haven't contributed before, a minor rewording or pure typo fix is generally not +suitable as a first contribution, but may be included as part of a more +substantial patch for an accepted ticket. See :doc:`/internals/contributing/writing-code/working-with-git` for more details on how to use pull requests.