Add a 'statement of intent' blurb to the top of MAINTAINERS. Split

the role of MAINTAINERS into advisory and strict parts. Introduce a
new LOCKS file to document enforced locked parts of the tree.

Strict locks are only added with core approval and will generally
have a renewal timeout.

Clarify that the source tree is a community effort, not a place to stake
out 'turf'.

This will be refined as needed.

With-core-hat-on:  Yes

1 files changed, 8 insertions, 0 deletions

diff --git a/LOCKS b/LOCKS
new file mode 100644
index 0000000..4f797d2
--- /dev/null
+++ b/LOCKS
@@ -0,0 +1,8 @@
+$FreeBSD$
+
+This file documents formal review/approval requirements that have been
+approved by core.
+
+subsystem       login   expires  notes
+--------------------------------------
+