CONTRIBUTING.txt 2.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  1. CONTRIBUTING TO MOODLE
  2. ======================
  3. Moodle is made by people like you. We are members of a big worldwide community
  4. of developers, designers, teachers, testers, translators and other users. We
  5. work in universities, schools, companies and other places. You are very welcome
  6. to join us and contribute to the project.
  7. See <https://docs.moodle.org/dev/Contributing_to_Moodle> for the many ways you
  8. can help, not only with coding.
  9. Moodle is open to community contributions to core, though all code must go
  10. through peer-review, automated behaviour testing, continuous integration and
  11. human post-integration checks.
  12. Pull requests
  13. -------------
  14. Please do not open pull requests via Github. The repository there is just a
  15. mirror of the official repository at <https://git.moodle.org>. Issues are
  16. reported and patches provided via <https://tracker.moodle.org>. See below for
  17. more information.
  18. Moodle core bug fixes and new features
  19. --------------------------------------
  20. During the years of intensive development, a mature process of including
  21. submitted patches has evolved.
  22. * Every bug fix or new feature must have a tracker issue.
  23. * You publish the branch implementing the fix or new feature in your public
  24. clone of the moodle.git repository (typically on Github).
  25. * Your patch is peer-reviewed, discussed, integrated, tested and then released
  26. as a part of moodle.git.
  27. * New features are developed on the master branch. Bug fixes are also
  28. backported to currently supported maintenance (stable) branches.
  29. For further details, see <https://docs.moodle.org/dev/Process>.
  30. Moodle plugins
  31. --------------
  32. Moodle has a framework for additional plugins to extend its functionality. We
  33. have a Moodle plugins directory <https://moodle.org/plugins/> where you can
  34. register and maintain your plugin. Plugins hosted in the plugins directory can
  35. be easily installed and updated via the Moodle administration interface.
  36. * You are expected to have a public source code repository with your plugin
  37. code.
  38. * After registering your plugin in the plugins directory it is reviewed before
  39. being published.
  40. * You are expected to continuously release updated versions of the plugin via
  41. the plugins directory. We do not pull from your code repository; you must do
  42. it explicitly.
  43. For further details, see <https://docs.moodle.org/dev/Plugin_contribution>.