Resolves #40 - add adoption.md to explain what OIE should do when adding code from other projects

adoption.md

@@ -0,0 +1,53 @@
+# Adoption of Other Projects
+
+The Open Integration Engine may adopt other projects. This includes, but is not limited to, forking other open source projects, donations of existing open source projects, or other intellectual property of value to Open Integration Engine and our community.
+
+## License Compatibilty
+
+Any project that OIE incorporates _MUST_ have an appropriate license.
+
+This is critical for code that is incorporated to our main repos - this code _MUST_ be under the same license as the repo it is incorporated to. 
+
+Code which is forked must have an appropriate license, preferably open-source that allows us to fork the project. The license must be clearly documented.
+
+## Categories
+
+### Forked
+
+Open-source is open. OIE will fork other open source projects under our organizational umbrella.
+
+We do this to preserve code, assist with other projects, and to otherwise support our work for the larger community.
+
+OIE will do this with general consensus from the [Steering Committee](steering_committee.md) and [Maintainers](maintainers.md). 
+
+### Maintained
+
+If you currently own or maintain plugin code which you think would benefit the community if it were hosted under the OIE umbrella, you may initiate a request to transfer maintainership of that plugin code to the project.
+
+Accepting the responsibility to maintain a project will be handled on a case-by-case basis, outside of the typical pull-request process. The steering committee and maintainers will review any projects offered under this category.
+
+### Incorporated
+
+After being forked or accepted as maintained, some projects may be incorporated to the OpenIntegrationEngine. These are projects which are especially valuable can be incorporated to our main repositories.
+
+This will be handled through our typical pull-request process. Any donated or forked repositories will be updated with documentation, links, flags, archival, etc. to indicate that they have been incorporated elsewhere.
+
+Projects which are incorporated from forks will, as much as is practical, be incorporated in a way which allows us to continue to collaborate with up- or down-stream projects.
+
+## Distributed
+
+OIE may choose to build and distribute these projects. When doing so OIE _MUST_:
+
+- ensure the projects are of sufficient quality and safety for their stated use
+- ensure that distributions from OIE are appropriately reviewed and scanned for risks, vulnerabilities, and security best-practices
+- ensure that distributions modified and built by OIE are signed by OIE 
+
+## Adopted Projects
+
+Adopted projects will have repositories set up with topics to represent their status. All adopted projects will have a topic of "Adopted" and then an additional topic representing their category.
+
+Search links for the repositories are:
+- [Forked](https://github.com/search?q=org%3AOpenIntegrationEngine+topic%3Aadopted+topic%3Aforked&type=repositories)
+- [Donated](https://github.com/search?q=org%3AOpenIntegrationEngine+topic%3Aadopted+topic%3Adonated&type=repositories)
+- [Incorporated](https://github.com/search?q=org%3AOpenIntegrationEngine+topic%3Aadopted+topic%3Aincorporated&type=repositories)
+- [Distributed](https://github.com/search?q=org%3AOpenIntegrationEngine+topic%3Aadopted+topic%3Adistributedd&type=repositories)