Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up licensing #171

Closed
Tracked by #189
remcowesterhoud opened this issue Feb 9, 2022 · 2 comments · Fixed by #211
Closed
Tracked by #189

Set up licensing #171

remcowesterhoud opened this issue Feb 9, 2022 · 2 comments · Fixed by #211
Assignees

Comments

@remcowesterhoud
Copy link
Contributor

remcowesterhoud commented Feb 9, 2022

Description

We need to properly license our code. None of this project is part of the core-business. Therefore the project can be licensed under the regular Apache 2 license.
One exception is the in memory engine. This module depends on the zeebe broker, which is part of the core-business. This means that the engine module must follow the same license as the zeebe broker.

What we need to do:

  1. Create a license folder like in zeebe (https://github.com/camunda-cloud/zeebe/tree/main/licenses) containing the apache license and the zeebe license.
  2. Add a section to the README and the Contribution Guide specifying that all modules are licensed under Apache 2, except for the engine which is licensed under the Zeebe license.
  3. Remove the LICENSE file
@remcowesterhoud remcowesterhoud changed the title Set up licensing properly Set up licensing Feb 9, 2022
This was referenced Feb 18, 2022
@pihme
Copy link
Contributor

pihme commented Mar 1, 2022

What about adding license/copyright headers to all source files and checking that these are there?

@remcowesterhoud
Copy link
Contributor Author

Another note: License gets added to the flatten pom. This is always Apache 2.0. For engine, engine-agent and extension these need to be changed to the Zeebe license.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants