mirror of
https://github.com/flectar/mail.git
synced 2026-11-11 17:57:54 +00:00
74 lines
3.4 KiB
Markdown
74 lines
3.4 KiB
Markdown
# Flectar Mail licensing
|
|
|
|
Flectar Mail is one open-source application. There is currently no separate
|
|
“community edition”, “commercial edition”, or proprietary Flectar Mail client.
|
|
|
|
## Open-source application
|
|
|
|
Unless a file or directory says otherwise, the Flectar-authored source code in
|
|
this repository is licensed under the GNU Affero General Public License,
|
|
version 3 only (`AGPL-3.0-only`). The complete terms are in [`LICENSE`](LICENSE).
|
|
|
|
The AGPL permits use, study, modification, redistribution, and commercial use.
|
|
When its conditions apply, distributors must provide corresponding source under
|
|
the same license. Modified versions offered for remote interaction must also
|
|
offer their corresponding source to those users.
|
|
|
|
Every client feature published in this repository, including integrations with
|
|
optional hosted services, remains under its stated open-source license.
|
|
Publishing a version under the AGPL is permanent: later business or licensing
|
|
decisions cannot revoke the rights already granted for that version.
|
|
|
|
## Optional paid services
|
|
|
|
Flectar may fund development by operating optional paid services that require
|
|
ongoing infrastructure, such as hosted encrypted synchronization, relays,
|
|
storage, managed processing, or support. A subscription purchases access to
|
|
that service; it does not purchase a differently licensed Flectar Mail client.
|
|
|
|
The software and operational configuration used to run a Flectar-hosted
|
|
service may be developed separately and may not be included in this repository.
|
|
Merely communicating with an independent service over a network does not place
|
|
that service in this repository or change the service's license. If a service
|
|
does copy, modify, or derive from AGPL-covered code, the AGPL continues to apply
|
|
according to its terms, including its network-source requirements.
|
|
|
|
No paid Flectar service or entitlement described here exists merely because it
|
|
is mentioned as a possible business model. Any actual offering will have its
|
|
own published scope, price, privacy terms, and service terms before launch.
|
|
|
|
## Contributions
|
|
|
|
Outside contributions are accepted under the license that applies to the files
|
|
being changed, usually `AGPL-3.0-only`. Contributors retain copyright and must
|
|
have the right to submit their work under that license. See
|
|
[`CONTRIBUTING.md`](CONTRIBUTING.md) for the contribution process.
|
|
|
|
## Trademarks
|
|
|
|
The software license does not grant rights to the Flectar name, the Flectar
|
|
Mail name, logos, application identifiers, or other brand assets. Forks remain
|
|
welcome under the AGPL, but distributed modified versions must follow
|
|
[`TRADEMARKS.md`](TRADEMARKS.md), including the renaming requirements.
|
|
|
|
## Third-party material
|
|
|
|
Dependencies, vendored components, fonts, and example brand marks retain their
|
|
own licenses and notices. They are documented in
|
|
[`THIRD_PARTY_NOTICES.md`](THIRD_PARTY_NOTICES.md) and the `LICENSES/`
|
|
directory. Flectar cannot offer commercial rights to material it does not own.
|
|
|
|
## Practical summary
|
|
|
|
| Use | Flectar Mail |
|
|
|---|---|
|
|
| Use privately or commercially | Yes |
|
|
| Modify or fork | Yes |
|
|
| Sell copies or services | Yes |
|
|
| Distribute a closed-source modified build | No |
|
|
| Use Flectar branding for a modified distribution | No |
|
|
| Use an optional Flectar-hosted service | Subject to that service's terms |
|
|
|
|
This document explains the project's licensing model; the applicable license
|
|
texts control if there is any conflict.
|