Code

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#10110 closed (fixed)

Add to contributing FAQ: tips on making better tickets and question on getting the core devs attention

Reported by: graham_king Owned by: nobody
Component: Documentation Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation:
Needs tests: Patch needs improvement:
Easy pickings: UI/UX:

Description

In this django-developers thread Russell and Karen provide valuable information on how to write a better ticket, and how and when to get the core devs attention on a ticket.

http://groups.google.com/group/django-developers/browse_thread/thread/7085109ceace2e37

This patch writes that up to be part of the FAQ.

Attachments (1)

10110.diff (2.6 KB) - added by graham_king 5 years ago.

Download all attachments as: .zip

Change History (3)

Changed 5 years ago by graham_king

comment:1 Changed 5 years ago by russellm

  • Resolution set to fixed
  • Status changed from new to closed

(In [9789]) Fixed #10110 -- Added FAQ on how and when to poke the core developers about tickets. Thanks to Graham King for turning a couple of django-dev posts into a good first draft.

comment:2 Changed 5 years ago by russellm

(In [9790]) [1.0.X] Fixed #10110 -- Added FAQ on how and when to poke the core developers about tickets. Thanks to Graham King for turning a couple of django-dev posts into a good first draft.

Merge of r9789 from trunk.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.