#29729: Update "Writing your first patch for Django" tutorial
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: Adam
Johnson | (Chainz) Johnson
Type: Uncategorized | Status: assigned
Component: Documentation | Version: 2.1
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Adam (Chainz) Johnson):
* cc: Adam (Chainz) Johnson (added)
* owner: nobody => Adam (Chainz) Johnson
* status: new => assigned
Comment:
I suspect moving to a later commit isn't a great idea as it'll just be a
moving target. I suggest instead some kind of "fake feature" in the
tutorial to implement, such as adding a new function to django.__init__.
This would also require less knowledge of the specifics of whatever real
tickets are touching, e.g. the current one is a fairly niche forms
feature. Thoughts anyone?
--
Ticket URL: <https://code.djangoproject.com/ticket/29729#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.192dc3b7a58f82965ce9d7d3fb9451c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
