#35546: Modernize contributing pages to aling with current requirement of
having an
accepted ticket for non trivial changes
------------------------------------------------+------------------------
Reporter: Natalia Bidart | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: dev
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
Following some feedback from https://github.com/django/django/pull/17389,
there are some parts in these docs:
https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-
features/
https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
/submitting-patches/
that could benefit from being more explicit about the need to have an
accepted ticket when working on non trivial changes.
Specifically, I think that this paragraph is misleading:
"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. Fork Django on GitHub,
create a feature branch, and show us your work!"
And also the patch review checklist should explicitly mention that an
accepted ticket is required to get reviews/discussion in a GH PR.
--
Ticket URL: <https://code.djangoproject.com/ticket/35546>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107019036e1d911-b948f28e-7d54-442b-93bb-aaabf2dbebb4-000000%40eu-central-1.amazonses.com.
