MAINTAINERS: Explain the format and reference other projects

wking · wking · commit a475e76156ae · 2016-09-08T22:26:08.000-07:00
Currently the OCI seems to have one repository per Project. A few repositories are not official projects; ocitools is just becoming official [1] and artwork [2] may never be a Project. But I expect that going forward, any opencontainers/ repos that have a MAINTAINERS file will be official Projects, so the union rule here should be both correct and easy to maintain. The file is not Markdown, so I've gone with my usual reference-style link instead of a Markdown reference-style link. [1]: opencontainers/tob#18 Subject: Create runtime-tools and image-tools projects [2]: https://github.com/opencontainers/artwork Signed-off-by: W. Trevor King <wking@tremily.us>
diff --git a/MAINTAINERS b/MAINTAINERS
@@ -0,0 +1,8 @@
+This meta-project is maintained by the union of MAINTAINERS for all OCI Projects [1].
+
+Other OCI Projects should list one maintainer per line, with a name, email address, and GitHub username:
+
+Random J Developer <random@developer.example.org> (@RandomJDeveloperExample)
+A. U. Thor <author@example.org> (@AUThorExample)
+
+[1]: https://github.com/opencontainers/

-Original file line number
+Diff line change
@@ @@ -0,0 +1,8 @@ @@
 +This meta-project is maintained by the union of MAINTAINERS for all OCI Projects [1].
++
 +Other OCI Projects should list one maintainer per line, with a name, email address, and GitHub username:
++
 +Random J Developer <[email protected]> (@RandomJDeveloperExample)
 +A. U. Thor <[email protected]> (@AUThorExample)
++
 +[1]: https://github.com/opencontainers/