Hi all, On Tue, Apr 20, 2010 at 8:34 AM, Gabriel Hurley <gab...@gmail.com> wrote:
> When I finally did submit my first patch, I was terrified of getting > it wrong and having it rejected. I'd seen it happen on other tickets. > As a project, I'm sure we don't want any (even potential) contributors to be terrified. How can we fix that, and encourage people to work with the process rather than deciding that Django is an elitist club and walking away? I've listed a couple of ideas below for enhancements to Trac to help a bit. What do people think? Worth spending time on? Rob :) Idea #1: When a ticket is currently closed Trac sends you an email saying "status:closed resolution:wontfix" and whatever comment is made by the person who closed it. How about a plugin for Trac that expands these ... "concise" emails with some docs and links, so reporters can (a) get a better explanation of why something has been changed, and (b) have a clear direction going forward. Just putting the comments in the email above the "resolution:wontfix" I think would provide a better (less emotional, more rational) experience for a reader. eg. Closed-as-Duplicate: " By closing duplicate tickets, we keep all the discussion about a topic in one place, which helps everyone. Your next steps: 1. Check out the linked ticket that is referred to above. 2. Add any relevant notes/patches/discussion from here to the other ticket. 3. If you don't agree that it's a duplicate, please reopen the ticket and explain why (mistakes do happen!). " likewise for the other resolutions, and also setting of custom fields (eg. needs_better_patch, needs_tests, needs_documentation). Idea #2: Have a tool that goes through open tickets and finds ones where the ticket is waiting on something (eg. docs) and nothing has happened for a while. It could email the owner and remind them that (a) Django does care, and (b) offer them some help: - suggest they add it to a "please i would love some help with (documentation)(tests)" page, along the lines of the "Little, easy improvements" page. - if its DDN, suggest they bring it up on django-developers - if they don't have time to work further on it, set the owner to nobody so it doesn't look like someone is "working" on it We could also run this a few weeks before feature-freeze so people can have a chance to add docs/tests to tickets, upgrade them to be trunk-ready, and not miss the bus for another release. And (has been suggested before?) try and automatically apply the latest patch on a ticket to trunk and add a comment if it stops applying cleanly. Rob :) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
