#24370: Recommend that all new projects use a custom user model
-------------------------------------+-------------------------------------
Reporter: carljm | Owner:
Type: | maestrofjp
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by maestrofjp):
* owner: nobody => maestrofjp
* status: new => assigned
Comment:
I'd like to help out by making the documentation change to reflect
whatever is decided. I'm assigning myself this ticket -- feel to steal it
back.
I agree @timgraham that modifying the default project template appears to
be way beyond the scope of this ticket. I think a good first step would be
massage the wording around this.
I'm relatively new Django developer (just a couple years) and the wording
around this is very scary. I originally was dissuaded from using a custom
user model, luckily we migrated to one before the application went to
production. However, the transition was still painful as all of our
migrations changed, etc.
If a consensus can be made, I'm happy to update the documentation. Please
advise next steps...
--
Ticket URL: <https://code.djangoproject.com/ticket/24370#comment:7>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.383b437f9d023698ef61da710f20e3d2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
