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