index.txt 3.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  1. ======================
  2. Contributing to Django
  3. ======================
  4. Django is a community that lives on its volunteers. As it keeps growing, we
  5. always need more people to help others. As soon as you learn Django, you can
  6. contribute in many ways:
  7. * Join the `Django forum`_. This forum is a place for discussing the Django
  8. framework and applications and projects that use it. This is also a good
  9. place to ask and answer any questions related to installing, using, or
  10. contributing to Django.
  11. * Join the |django-users| mailing list and answer questions. This
  12. mailing list has a huge audience, and we really want to maintain a
  13. friendly and helpful atmosphere. If you're new to the Django community,
  14. you should read the `posting guidelines`_.
  15. * Join the `#django IRC channel`_ on Freenode and answer questions. By
  16. explaining Django to other users, you're going to learn a lot about the
  17. framework yourself.
  18. * Blog about Django. We syndicate all the Django blogs we know about on
  19. the `community page`_; if you'd like to see your blog on that page you
  20. can `register it here`_.
  21. * Contribute to open-source Django projects, write some documentation, or
  22. release your own code as an open-source pluggable application. The
  23. ecosystem of pluggable applications is a big strength of Django, help us
  24. build it!
  25. If you think working *with* Django is fun, wait until you start working *on*
  26. it. We're passionate about helping Django users make the jump to contributing
  27. members of the community, so there are several ways you can help Django's
  28. development:
  29. * :doc:`Report bugs <bugs-and-features>` in our `ticket tracker`_.
  30. * Join the |django-developers| mailing list and share your ideas for how
  31. to improve Django. We're always open to suggestions. You can also interact
  32. on the `#django-dev IRC channel`_.
  33. * :doc:`Submit patches <writing-code/submitting-patches>` for new and/or
  34. fixed behavior. If you're looking for a way to get started contributing
  35. to Django read the :doc:`/intro/contributing` tutorial and have a look at the
  36. `easy pickings`_ tickets. The :ref:`patch-review-checklist` will also be
  37. helpful.
  38. * :doc:`Improve the documentation <writing-documentation>` or
  39. :doc:`write unit tests <writing-code/unit-tests>`.
  40. * :doc:`Triage tickets and review patches <triaging-tickets>` created by
  41. other users.
  42. Really, **ANYONE** can do something to help make Django better and greater!
  43. Browse the following sections to find out how:
  44. .. toctree::
  45. :maxdepth: 2
  46. new-contributors
  47. bugs-and-features
  48. triaging-tickets
  49. writing-code/index
  50. writing-documentation
  51. localizing
  52. committing-code
  53. .. _posting guidelines: https://code.djangoproject.com/wiki/UsingTheMailingList
  54. .. _#django IRC channel: irc://irc.freenode.net/django
  55. .. _#django-dev IRC channel: irc://irc.freenode.net/django-dev
  56. .. _community page: https://www.djangoproject.com/community/
  57. .. _Django forum: https://forum.djangoproject.com/
  58. .. _register it here: https://www.djangoproject.com/community/add/blogs/
  59. .. _ticket tracker: https://code.djangoproject.com/
  60. .. _easy pickings: https://code.djangoproject.com/query?status=!closed&easy=1