Skip to content

Commit cb5e152

Browse files
committed
Resolves #40 - add adoption.md to explain what OIE should do when adding code from other projects
Signed-off-by: jonbartels <jonathan.bartels@gmail.com>
1 parent 937dca1 commit cb5e152

1 file changed

Lines changed: 54 additions & 0 deletions

File tree

adoption.md

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
# Adoption of Other Projects
2+
3+
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.
4+
5+
## License Compatibilty
6+
7+
Any project that OIE incorporates _MUST_ have an appropriate license.
8+
9+
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.
10+
11+
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.
12+
13+
## Categories
14+
15+
### Forked
16+
17+
Open-source is open. OIE will fork other open source projects under our organizational umbrella.
18+
19+
We do this to preserve code, assist with other projects, and to otherwise support our work for the larger community.
20+
21+
OIE will do this with general consensus from the [Steering Committee](steering_committee.md) and [Maintainers](maintainers.md).
22+
23+
### Donated
24+
25+
OIE has already had several donors assign copyright of their work to OIE. These donors generously supported the project with their work. This lets OIE own and maintain projects which valuable to the community.
26+
27+
Donations of entire projects are accepted on a case-by-case basis, outside of the typical pull-request process. The steering committee, with input from maintainers, will review any offered donations.
28+
29+
We will generally request assignment of copyright for donated projects. This is what differentiates a donation from a fork. Assignment of copyright to OIE represents us
30+
31+
### Incorporated
32+
33+
After being forked or donated, some projects may be incorporated to the OpenIntegrationEngine. These are projects which are especially valuable can be incorporated to our main repositories.
34+
35+
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.
36+
37+
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.
38+
39+
## Distribution
40+
41+
OIE may choose to build and distribute these projects. When doing so OIE _MUST_:
42+
43+
- ensure the projects are of sufficient quality and safety for their stated use
44+
- ensure that distributions from OIE are appropriately reviewed and scanned for risks, vulnerabilities, and security best-practices
45+
- ensure that distributions modified and built by OIE are signed by OIE
46+
47+
## Adopted Projects
48+
49+
- Forked
50+
- [TLS Plugin](https://github.com/OpenIntegrationEngine/tls-manager-plugin) from NovaMap and Diridium
51+
- Donated
52+
- [LDAP Plugin](https://github.com/OpenIntegrationEngine/ldap-plugin) from Christopher Schulz
53+
- [MFA Plugin](https://github.com/OpenIntegrationEngine/mfa-plugin) from Christopher Schulz
54+
- Incorporated

0 commit comments

Comments
 (0)