Since ages ago we have had different requests/proposals to better separate/decide about the availability of the admin->development subtree.

The last one was MDL-42823, where a custom solution (rejected) was proposed to control the new "generators" stuff.

So this is about to discuss and decide the way to implement that ability that will lead to a better separation of the "admin" and "dev" conceptual roles, making everybody happier.

FACTS:

1) The admin->development subtree contents is really heterogeneous:

• there are some items being simple settings.
• there are some items being a specialized core admin page.
• there are some items being a local plugin.
• there are some items being a tool plugin.
• there are some bundled with core.
• there are some being contrib plugins (by moodlehq)

2) Right now, the subtree is shown to everybody (any admin) by default

3) There are people asking for some way to get rid of it. (any non-developer admin around the world).

GOALS:

1) Decide if this should be solved globally (make the whole subtree hidden) or item by item.
2) Decide if this must be solved using some standard moodle technique (plugins handling) or with a custom one.
3) Decide the default status (hidden/shown) for a new installation.

POSSIBLE SOLUTIONS (feel free to add more and observe numbering):

A) One simple global switch ($CFG->im_a_developer or $CFG->hide_that_please are the alternatives) doing the magic and deciding to show/hide the whole subtree.

B) Convert all the items to proper plugins and then use standard plugin abilities to enable/disable install/uninstall them (to implement too).

C) Have some extra permission (moodle:born_to_hack) causing the items to be shown.

D) Use some user-based solution (list of users with access to). Much like MDL-36687, but about the admin subtree.

E) Consider moving all them to contrib area, so they aren't installed by default anymore.

F) Any combination of the above.

And that's the problem, the goals and the possible solutions. Enjoy discussing!