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--------
 8
 9### Installation
10
11
12<a href="https://repology.org/project/zed-editor/versions">
13    <img src="https://repology.org/badge/vertical-allrepos/zed-editor.svg?minversion=0.143.5" alt="Packaging status" align="right">
14</a>
15
16On macOS and Linux 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).
17
18Other platforms are not yet available:
19
20- Windows ([tracking issue](https://github.com/zed-industries/zed/issues/5394))
21- Web ([tracking issue](https://github.com/zed-industries/zed/issues/5396))
22
23### Developing Zed
24
25- [Building Zed for macOS](./docs/src/development/macos.md)
26- [Building Zed for Linux](./docs/src/development/linux.md)
27- [Building Zed for Windows](./docs/src/development/windows.md)
28- [Running Collaboration Locally](./docs/src/development/local-collaboration.md)
29
30### Contributing
31
32See [CONTRIBUTING.md](./CONTRIBUTING.md) for ways you can contribute to Zed.
33
34Also... we're hiring! Check out our [jobs](https://zed.dev/jobs) page for open roles.
35
36### Licensing
37
38License information for third party dependencies must be correctly provided for CI to pass.
39
40We use [`cargo-about`](https://github.com/EmbarkStudios/cargo-about) to automatically comply with open source licenses. If CI is failing, check the following:
41
42- 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.
43- 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`.
44- 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).