diff --git a/docs/internals/contributing.txt b/docs/internals/contributing.txt
index 399e458..db1f511 100644
a
|
b
|
of the community, so there are many ways you can help Django's development:
|
15 | 15 | served up. |
16 | 16 | |
17 | 17 | * Submit patches for new and/or fixed behavior. Please read `Submitting |
18 | | patches`_, below, for details on how to submit a patch. |
| 18 | patches`_, below, for details on how to submit a patch. If you're looking |
| 19 | for a way to start contributing to Django have a look at the `easy-pickings`_ |
| 20 | tickets. |
19 | 21 | |
20 | 22 | * Join the `django-developers`_ mailing list and share your ideas for how |
21 | 23 | to improve Django. We're always open to suggestions, although we're |
… |
… |
members can do to help the triage process. In particular, you can help out by:
|
354 | 356 | * Correcting the "Needs tests", "Needs documentation", or "Has patch" flags |
355 | 357 | for tickets where they are incorrectly set. |
356 | 358 | |
| 359 | * Adding the `easy-pickings`_ keyword to tickets that are small and relatively |
| 360 | straightforward. |
| 361 | |
357 | 362 | * Checking that old tickets are still valid. If a ticket hasn't seen |
358 | 363 | any activity in a long time, it's possible that the problem has been |
359 | 364 | fixed but the ticket hasn't yet been closed. |
… |
… |
requests for commit access are potential flame-war starters, and will be ignored
|
1226 | 1231 | .. _pep8.py: http://pypi.python.org/pypi/pep8/ |
1227 | 1232 | .. _i18n branch: http://code.djangoproject.com/browser/django/branches/i18n |
1228 | 1233 | .. _`tags/releases`: http://code.djangoproject.com/browser/django/tags/releases |
| 1234 | .. _`easy-pickings`: http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&keywords=~easy-pickings&order=priority |