search

zed-industries / zed

Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
https://zed.dev
Other
48.24k stars 2.86k forks source link

License clarification #14753

Open t-c-acc opened 2 months ago

t-c-acc commented 2 months ago

Check for existing issues

Describe the feature

Issue

It should be made clear whether the binaries from zed.dev are compiled from the github source code, or from modified source code.

Since the binaries at the download page of zed.dev are provided with a different license than the source code (https://zed.dev/eula), and this license does not make it clear whether the editor downloaded is actually open source (Section 2.3: "certain versions of the Editor"), a user cannot be sure what license the software they downloaded is under.

I am not sure if it is a legal problem or not (that's why I'm making a Feature Request and not a Bug Report), I am making this issue for clarity for the users.

Additionally, I assume that the binaries in the Releases page of the github repo are compiled directly from the github source code, and thus are provided with the licenses present at the repo, not the EULA at zed.dev. Maybe this should be clarified as well.

Full Section 2.3 of the EULA

2.3. Open Source Software

Zed makes certain versions of the Editor and related software available at the Zed GitHub Repository: https://github.com/zed-industries/zed (the “Repo”). Your use of such software is subject to the open source software licenses declared in the Repo.

If applicable, add mockups / screenshots to help present your vision of the feature

No response

ConradIrwin commented 2 months ago

To clarify the build side: the binaries we distribute on zed.dev are the same binaries built from the repo via the Github actions.

On the license side paging @ballyhoojack who was looking into this; definitely agree we should clear this up.

JosephTLyons commented 2 months ago

cc: @notpeter - again, as the person who has a bit of knowledge on licensing.

t-c-acc commented 2 months ago

(closed the issue by mistake)

To clarify the build side: the binaries we distribute on zed.dev are the same binaries built from the repo via the Github actions.

The thing is that this can change at any point, if it is decided to include some non-free code in the binary.

t-c-acc commented 2 months ago

OK, so I assume the situation is similar to Chrome/Chromium and VSCode/Code-OSS: basically a proprietary program based on an open-source project. So far, according to @ConradIrwin, it happens that the proprietary binaries are exactly the same as the GPL-licensed ones, but that could change in the future without the need to notify the users.

Again, some transparency on this point would be good.

iilyak commented 1 month ago

Again, some transparency on this point would be good.

Agree it is very confusing. Some clarifications in README.md are needed. Is the binary published in gihub release a:

  1. At the user choice one of the AGPL / ASF / GPL
  2. Proprietary according to EULA with some components under the mentioned licenses

What about building from source?