The Lead source control management tool.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
cli
lib
vendor
.gitignore
.travis.yml
LICENSE
Makefile
README.md
configure
lock.json
main.go
manifest.json

README.md

Lead pb

travis Go Report Card GoDoc

Lead is a distributed version control system (DVCS); it aims to replace Git.

Git doesn’t so much have a leaky abstraction as no abstraction. There is essentially no distinction between implementation detail and user interface. – Steve Bennett

Short-term Goals

  • Provide a simplified* Git-like experience for version control.
  • Furthermore, reach feature-parity with Git with select exceptions (TBD).

Long-term Goals

  • Lead will be self-hosting. No third-party (like GitHub) will be necessary to open pull-requests, perform code-reviews, etc. Everything can be performed either via HTML (pb serve localhost:8080) or on the CLI.
  • Lead will not need a full-checkout in 'lazy' mode. Instead blobs and trees will be lazy-loaded from any peer providing the SHA256 hash of the object. This is so that Lead can adequately host extremely large projects that preclude a full-checkout†.

Can I use Lead yet?

No. Major features are in progress or have yet to be implemented.

Testing, Building, and Installing

Assert you've downloaded the repository and configured your PATH and GOPATH correctly.

Option A: For use

$ ./configure && make install

Option B: For development

# Install dependencies
$ ./configure

# Running unit tests
$ make test

# Building
$ make build

Contributing

Suggestions, comments, patches and other contributions are welcome. When you feel as if your contribution is ready, simply open a pull-request. Here are some basic rules about contributions:

  • I have strong notions of unity and harmony of software. This means that I may rewrite any patch suggestion, if only to keep the coding style consistent, or to better match long-term goals that I have not made explicit.
  • If I reject a suggestion, I will normally explain why, though I cannot promise that the explanation will be convincing. Even rejected suggestions have value, since they force me to put the underlying concepts into words.
  • Resulting code uses the BSD-3-Clause license, listing me (and only me) as the author. I will still list contributors in a section below.

This contribution guide was inspired by (i.e. stolen from) BearSSL's contribution guide.

Contributors

Inspiration

*Git is known to have a bloated, unclear user interface. Such problems have attempted to be solved in the past by providing new abstractions over Git. Lead aims to replace Git.

†Companies with monolithic repos and GBs of history (e.g. Microsoft Windows) cannot realistically be downloaded to a single hard-drive. Even if it could, forcing each developer to download the complete history would take an incredible amount of time. See below.

$ time git clone https://github.com/torvalds/linux.git
Cloning into 'linux'...
remote: Counting objects: 5163320, done.
remote: Compressing objects: 100% (3066/3066), done.
remote: Total 5163320 (delta 2158), reused 306 (delta 306), pack-reused 5159939
Receiving objects: 100% (5163320/5163320), 1.67 GiB | 761.00 KiB/s, done.
Resolving deltas: 100% (4269857/4269857), done.
Checking connectivity... done.
Checking out files: 100% (57202/57202), done.

real	44m28.483s
user	3m45.883s
sys	2m11.837s