Does "fully community supported" warrant an update of LICENSE.txt?
alexeyqu opened this issue · comments
Hi team,
I wonder if the September 15th, 2023 move to "fully community supported" model and the "We encourage the community to fork this repository for continued development and contributions." statement warrant an update of LICENSE.txt?
Currently it outlines a mix of MIT, GNU AGPL v.3.0 and commercial license, as follows:
You are licensed to use compiled versions of Focalboard produced by Mattermost, Inc. under an MIT LICENSE
- See MIT-COMPILED-LICENSE.md included in compiled versions for details
You may be licensed to use source code to create compiled versions not produced by Mattermost, Inc. in one of two ways:
1. Under the Free Software Foundation’s GNU AGPL v.3.0, subject to the exceptions outlined in this policy; or
2. Under a commercial license available from Mattermost, Inc. by contacting commercial@mattermost.com
You are licensed to use the source code in Admin Tools and Configuration Files (webapp/html-templates/, app-config.json,
config.json, webapp/i18n/, server/model/, plugin/ and all subdirectories thereof) under the Apache License v2.0.
We promise that we will not enforce the copyleft provisions in AGPL v3.0 against you if your application (a) does not
link to Focalboard directly, but exclusively uses Focalboard's Admin Tools and Configuration Files, and
(b) you have not modified, added to or adapted the source code of Focalboard in a way that results in the creation of
a “modified version” or “work based on” Focalboard as these terms are defined in the AGPL v3.0 license.
I am not sure to what extent it reflects the "community supported" model. It sounds like patched and self-hosted deployments may need to be careful in using the Focalboard name / logo and/or any © signs if they are displayed somewhere in the app(s).
Any advice?
P.S. I am a developer, not a lawyer.
Hi @alexeyqu, thanks for this thoughtful question. This is new territory for us too, so we're discussing internally on how to best proceed and support future contributors like you.
That may entail altering the licensing, but I don't have an answer for you quite yet. I ran your question by our team and hope to provide some further guidance in the near future. Thanks again! 👨💻