Replies: 1 comment
-
As this discussion was initially spawned by #408 and under the impression of a rediscovered #1199 a new proposal has been made in #408 (comment): Plane and GitLab could be prime examples for showing open integrations between open core products, by allowing that integrations between them are considered just that: open. This leaves the option to integrate with only commercially available platforms only with a paid license. Can we imagine to introduce the distinction of differentiating the GitLab integration from the GitHub integration in so far, that we allow people depending on and contributing to the open spirit, such as external contributors which sign the CLA, to integrate with the open core? Integration with premium GitLab plans and the features offered through that could also remain restricted to an audience in an ongoing client relationship to Plane. |
Beta Was this translation helpful? Give feedback.
-
In #408 we have described a case in which a contributor from the Free and Open Source movement cannot contribute an implementation for the integrations feature set, which is restricted to enterprise licensing.
While recognition to the signers of the CLA is given in the release notes, there is no further privilege attached to signing the CLA, while all rights are waived and transferred to Plane.
Would it appear considerable to extend the CLA in a form, that it allows its signers to contribute to all parts of the application, by providing them a life time enterprise license in return for their intellectual property rights?
Beta Was this translation helpful? Give feedback.
All reactions