#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):
OK, I read again and see. My first impression was not representative here.
Really everything is covered in
[https://docs.djangoproject.com/en/1.9/internals/contributing/]. It's
quite a lot to read for new contributors like me, but it is needed to get
a full overview of the process.
I see a minor issue that the section
[https://docs.djangoproject.com/en/1.9/internals/contributing/writing-code
/working-with-git/] is also important when triaging tickets (code
reviewing/testing), writing documentation and committing code. Maybe it is
possible to move this section more up in the hierarchy, but I seen no good
place to add it elsewhere. Or maybe in
[https://docs.djangoproject.com/en/1.9/internals/contributing/new-
contributors/#first-steps]?
When the role of GitHub in the ticket process is clearly pointed out, then
I consider this issue to be solved.
--
Ticket URL: <https://code.djangoproject.com/ticket/26359#comment:5>
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.c91948bd8ef92a919a44d587755baadb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
