Document terms for core plugins
Bug: Issue 11636
Change-Id: Iaa3b6201439c8fd32c62dbcac12df538be101451
Signed-off-by: Edwin Kempin <ekempin@google.com>
diff --git a/Documentation/dev-core-plugins.txt b/Documentation/dev-core-plugins.txt
index b70372f..2e84451 100644
--- a/Documentation/dev-core-plugins.txt
+++ b/Documentation/dev-core-plugins.txt
@@ -12,8 +12,19 @@
submodules] in the `gerrit` repository. E.g. this means they can be easily
link:dev-readme.html#clone[cloned] together with Gerrit.
-The core plugins are developed and maintained by the Gerrit maintainers
-and the Gerrit community.
+All core plugins are developed and maintained by the
+link:dev-roles.html#maintainers[Gerrit maintainers] and everyone can
+link:dev-contributing.html[contribute] to them.
+
+Adding a new core plugin feature that is large or complex requires a
+link:dev-design-doc.html[design doc] (also see
+link:dev-contributing.html#design-driven-contribution-process[design-driven
+contribution process]). The link:dev-processes.html#steering-committee[
+engineering steering committee (ESC)] is the authority that approves the design
+docs. The ESC is also in charge of adding and removing core plugins.
+
+Non-Gerrit maintainers cannot have link:access-control.html#category_owner[
+Owner] permissions for core plugins.
[[list]]
== Which core plugins exist?
