License properly as MIT, and include the Four Opens

The Four Opens are how I expect this project to be run and participated in.

LICENSE.txt

@@ -0,0 +1,22 @@
+The MIT License
+
+Copyright (c) 2018 CloudBees, Inc, and a number of other contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+

README.adoc

@@ -42,3 +42,47 @@ standard Jenkins components and Node.js.
 Everything should be easily executed via some Docker tooling behind `make`. To
 run tests for example, simply run `make check` in the root directory of this
 repository.
+
+=== The Four Opens
+
+Inspired by the Openstack project
+footnote:[https://governance.openstack.org/tc/reference/opens.html]
+Jenkins Essentials follows "The Four Opens":
+
+==== Open Source
+
+We do _not_ produce “open core” software.
+
+We are committed to creating truly open source software that is usable and
+scalable. Truly open source software is not feature or performance limited and
+is not crippled.
+
+
+We use the MIT license.
+
+
+
+==== Open Design
+
+*We are committed to an open design process.*  The development cycle requires
+active collaboration to gather requirements and write specifications for
+upcoming releases. Those events, which are *open to anyone,* include users,
+developers, and upstream projects. We gather requirements, define priorities
+and flesh out technical design to guide development for the next development
+cycle.
+
+The community controls the design process. You can help make this software meet
+your needs.
+
+==== Open Development
+
+We maintain a publicly available source code repository through the entire
+development process. We do public code reviews. We have public roadmaps. This
+makes participation simpler, allows users to follow the development process and
+participate in QA at an early stage.
+
+==== Open Community
+
+One of our core goals is to maintain a healthy, vibrant developer and user
+community. Most decisions are made using a lazy consensus model. All processes
+are documented, open and transparent.