#26359: explain dual ticket tracking system
-------------------------------------+-------------------------------------
Reporter: beckastar | Owner:
Type: | kaifeldhoff
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by kaifeldhoff):
I additionally noticed, that the Trac-Wiki
[https://code.djangoproject.com/wiki] also has a bold note for the use of
GitHub. It would be perfect if this kind of highlighting also occurs in
the docs.
I favor [https://docs.djangoproject.com/en/1.9/internals/contributing/new-
contributors/#first-steps]. We could add a second point in the first list
like this:
'''Learn how to work with Git and GitHub'''
No matter if code or documentation, everything finds its way into
Django through GitHub. If you are not familiar with Git start here:
[https://docs.djangoproject.com/en/1.9/internals/contributing/writing-code
/working-with-git/]
--
Ticket URL: <https://code.djangoproject.com/ticket/26359#comment:6>
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/067.27347578ef2adc830b321fc318ce00cd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
