1# 🚧 TODO 🚧
 2
 3- [ ] Add intro
 4- [ ] Add link to contributing guide
 5- [ ] Add barebones running zed from source instructions
 6- [ ] Link out to further dev docs
 7
 8# Zed
 9
10[![CI](https://github.com/zed-industries/zed/actions/workflows/ci.yml/badge.svg)](https://github.com/zed-industries/zed/actions/workflows/ci.yml)
11
12Welcome 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).
13
14## Developing Zed
15
16- [Building Zed](./docs/src/developing_zed__building_zed.md)
17- [Running Collaboration Locally](./docs/src/developing_zed__local_collaboration.md)
18
19### Licensing
20
21License information for third party dependencies must be correctly provided for CI to pass.
22
23We use [`cargo-about`](https://github.com/EmbarkStudios/cargo-about) to automatically comply with open source licenses. If CI is failing, check the following:
24
25- 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.
26- 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`.
27- 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).