= Reports = This page presents a list of useful queries into our ticket system. If you're looking to contribute to Django, whether you're a hardcore Python hacker or a complete newbie, below you'll find clear lists of what needs to be done. For people with skills in documentation, we've split out reports that include documentation-only tickets. = New contributors = Easy-pickings - how about contributing an easy patch to get started? * [query:status=!closed&stage=Accepted&easy=1 Tickets tagged "easy-pickings"] * [query:status=!closed&stage=Accepted&component=Documentation&has_patch=0 Documentation tickets needing patches] (often easy) = Intermediate contributors = Any experienced member of the community, or any reasonably experienced Python/web developer, is welcome to start work on these, and as a community run project with a small core team, we '''absolutely rely''' on these contributions! Remember to consult our [http://docs.djangoproject.com/en/dev/internals/contributing/#ticket-triage ticket triage policy], and also remember you can add more filters to these reports to select the components you have experience with. Thanks! == Reviewing tickets == These new tickets need work to see: 1. if reported bugs are really bugs or 2. if suggested features are sensible features to be added They may also need to have the component changed and other meta-data set. * [query:status=!closed&stage=Unreviewed Unreviewed tickets] == Reviewing patches == These tickets have been accepted and have patches, but someone needs to review the patch for quality, checking docs and tests. * [query:status=!closed&stage=Accepted&needs_better_patch=0&needs_tests=0&needs_docs=0&has_patch=1 Patches that need review] * [query:status=!closed&stage=Accepted&needs_better_patch=0&needs_tests=0&needs_docs=0&has_patch=1&component=Documentation Documentation patches that need review] When done, either set to 'Ready for checkin' or the relevant flags regarding patch quality, docs and tests. = Experienced contributors = Once you're ready to actually start on possibly-difficult problems, these tickets contain requests that have been accepted but have no patches, or patches that are not up to scratch, or are missing docs or tests. * [query:status=!closed&has_patch=0&stage=Accepted&or&status=!closed&needs_better_patch=1&stage=Accepted&or&status=!closed&needs_docs=1&stage=Accepted&or&status=!closed&needs_tests=1&stage=Accepted All tickets that need any implementation work] Broken down a bit further: * [query:status=!closed&stage=Accepted&has_patch=0 Tickets that need patches] * [query:status=!closed&stage=Accepted&has_patch=1&needs_better_patch=1 Tickets that have patches but need to be improved] * [query:status=!closed&stage=Accepted&needs_docs=1 Tickets that need documentation] * [query:status=!closed&stage=Accepted&needs_tests=1 Tickets that need unit tests] * [query:status=!closed&stage=Accepted&has_patch=1&needs_tests=0&needs_docs=1&needs_better_patch=0 Tickets that only need documentation] * [query:status=!closed&stage=Accepted&has_patch=1&needs_tests=1&needs_docs=0&needs_better_patch=0 Tickets that only need unit tests] * [query:status=!closed&stage=Accepted&has_patch=0&component=Documentation Documentation tickets that need patches] Once a patch is implemented, someone else will need to review it. = Core developers = Decision work: * [query:"status=!closed&stage=Design decision needed" Tickets that need a design decision] Commit work: * [query:"status=!closed&stage=Ready for checkin" Tickets that are ready for checkin] * [query:"status=!closed&stage=Ready for checkin&component=Documentation" Documentation tickets that are ready for checkin] High priority bugs: * [query:"status=!closed&severity=Release blocker" Release blockers]