1# Zed
 2
 3[![CI](https://github.com/zed-industries/zed/actions/workflows/ci.yml/badge.svg)](https://github.com/zed-industries/zed/actions/workflows/ci.yml)
 4
 5Welcome to Zed, a high-performance, multiplayer code editor from the creators of [Atom](https://github.com/atom/atom) and [Tree-sitter](https://github.com/tree-sitter/tree-sitter).
 6
 7## Installation
 8
 9You can [download](https://zed.dev/download) Zed today for macOS (v10.15+).
10
11Support for additional platforms is on our [roadmap](https://zed.dev/roadmap):
12
13- Linux ([tracking issue](https://github.com/zed-industries/zed/issues/7015))
14- Windows ([tracking issue](https://github.com/zed-industries/zed/issues/5394))
15- Web ([tracking issue](https://github.com/zed-industries/zed/issues/5396))
16
17For macOS users, you can also install Zed from Homebrew:
18```sh
19brew install zed
20```
21
22## Developing Zed
23
24- [Building Zed for macOS](./docs/src/developing_zed__building_zed_macos.md)
25- [Building Zed for Linux](./docs/src/developing_zed__building_zed_linux.md)
26- [Building Zed for Windows](./docs/src/developing_zed__building_zed_windows.md)
27- [Running Collaboration Locally](./docs/src/developing_zed__local_collaboration.md)
28
29## Contributing
30
31See [CONTRIBUTING.md](./CONTRIBUTING.md) for ways you can contribute to Zed.
32
33## Licensing
34
35License information for third party dependencies must be correctly provided for CI to pass.
36
37We use [`cargo-about`](https://github.com/EmbarkStudios/cargo-about) to automatically comply with open source licenses. If CI is failing, check the following:
38
39- Is it showing a `no license specified` error for a crate you've created? If so, add `publish = false` under `[package]` in your crate's Cargo.toml.
40- Is the error `failed to satisfy license requirements` for a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to the `accepted` array in `script/licenses/zed-licenses.toml`.
41- Is `cargo-about` unable to find the license for a dependency? If so, add a clarification field at the end of `script/licenses/zed-licenses.toml`, as specified in the [cargo-about book](https://embarkstudios.github.io/cargo-about/cli/generate/config.html#crate-configuration).