Hi all, Regarding http://code.djangoproject.com/wiki/Reports
It appears to me that this reports page is not nearly as useful as it could be, and I'm thinking of redesigning it. To me, it seems it should structured by the *role* of people who might be involved in Django development, perhaps something like this: ----------------- = New contributors = Easy-pickings - how about contributing a patch for something that should be easy? For documentation only fixes: [link] Other fixes: [link] = Experienced contributors = Any experienced member of the community is welcome to start work on these. Remember you can use more filters to these reports to select the components you have experience with etc. == Reviewing tickets == These new tickets need work to see: 1) if they are really bugs or 2) if they are sensible features to be added They may also need to have the category changed and other meta-data set. [link] == Reviewing patches == These tickets have been accepted and have patches, but someone needs to review the patch for quality, checking docs and tests. For documentation only fixes: [link] Other fixes: [link] When done, either set 'Ready for checkin' or the relevant flags regarding patch quality, docs and tests. == Implementing patches == These tickets are accepted but have no patches, or patches that are not up to scratch, or are missing docs or tests. For documentation only fixes: [link] Other fixes: [link] Tickets that just need tests: [link] Tickets that just need docs: [link] Popular tickets (more than 15 on CC list): [link] Once a patch is implemented, someone else will need to review it. = Core developers = Tickets that should be ready for checkin, and just need a core developer to commit them. For documentation only fixes: [link] Other fixes: [link] ------------------- The idea is to help people understand the different roles without them having to read all our docs about contributing, and to enable people to know what is considered appropriate action for them. What do people think? Are there things present in the current reports page that I have missed in the above and are really useful? I don't think the 'Claimed tickets' report is at all useful, and many of the others are not really useful as they get lost in the list. BTW, if this is agreed on, and someone else would like to do the changes, that would be *great*. Thanks, Luke -- "I am going to let you move around more, just to break up the mahogany." (True Quotes From Induhviduals, Scott Adams) Luke Plant || http://lukeplant.me.uk/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
