1# Zed
 2
 3[![Zed](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/zed-industries/zed/main/assets/badge/v0.json)](https://zed.dev)
 4[![CI](https://github.com/zed-industries/zed/actions/workflows/ci.yml/badge.svg)](https://github.com/zed-industries/zed/actions/workflows/ci.yml)
 5
 6Welcome 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).
 7
 8---
 9
10### Installation
11
12On macOS, Linux, and Windows you can [download Zed directly](https://zed.dev/download) or [install Zed via your local package manager](https://zed.dev/docs/linux#installing-via-a-package-manager).
13
14Other platforms are not yet available:
15
16- Web ([tracking issue](https://github.com/zed-industries/zed/issues/5396))
17
18### Developing Zed
19
20- [Building Zed for macOS](./docs/src/development/macos.md)
21- [Building Zed for Linux](./docs/src/development/linux.md)
22- [Building Zed for Windows](./docs/src/development/windows.md)
23- [Running Collaboration Locally](./docs/src/development/local-collaboration.md)
24
25### Contributing
26
27See [CONTRIBUTING.md](./CONTRIBUTING.md) for ways you can contribute to Zed.
28
29Also... we're hiring! Check out our [jobs](https://zed.dev/jobs) page for open roles.
30
31### Licensing
32
33License information for third party dependencies must be correctly provided for CI to pass.
34
35We use [`cargo-about`](https://github.com/EmbarkStudios/cargo-about) to automatically comply with open source licenses. If CI is failing, check the following:
36
37- 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.
38- 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`.
39- 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).