1. What is gitdot?

A better GitHub.
A home for great open-source software.

2. Who is gitdot for?

Developers.
People who care. People who see code as more than a means to an end, but as a craft to perfect.
People who build software well — not because it is the optimal thing to do, but because it is the right thing to do.

3. What problem does gitdot solve?

Quality.
Open-source software only has one competitive platform: GitHub. And while GitHub is an impressive product, we also know that a lack of competition enables degradation over time. There's a few pain points we're keenly aware of (e.g., CI) and make it our mission to build a better alternative.

4. What features will gitdot have?

• A hyper-performant Git server written in Rust.
• A code review tool that uses stacked diffs as primitive
• A sane CI/CD platform that is secure by design, locally testable and reproducible

We think things could be a lot better — and we want to release features that we're proud of.
That does mean that things will take time, as building software right is still hard, but we do think you'll find it worth it.

5. What features will gitdot not have?

AI.
We view AI as an implementation detail — and do not think that using it is necessarily good.
In fact, we think it makes many products worse by acting as a bandaid for poor design.
That isn't to say we are blind to it, but that we will be judicious in our use of it instead.

6. When will gitdot have XYZ?

We publicize our roadmap in /releases with estimated dates for each.
While we do think that stands to be pretty complete, if there is something missing, please do let us know.

7. How does gitdot make money?

We don't.
We are fortunate enough to have raised a small pre-seed round from investors we are happy to call friends, and also to be at a point in our lives where we are financially independent and in good health.

But it is our intention to build a business that lasts.
And we will be unabashed in looking for honest and sustainable ways to profit.
As of now, all repositories are free, but we do envision charging for private repositories for teams in the future.

8. Does gitdot sell or train on my data?

We do not.
There are fewer things lamer than selling data for profit.
Your code is your own and there should not be a thing to say otherwise.

We make this promise in our privacy policy, but also know that even the law is not enough in matters of sovereignty, so plan to build an end-to-end encrypted git protocol as well.

9. Is gitdot open source?

Yes. gitdot uses the Apache License.
We are committed to open-source, but also do acknowledge the fear of a rug pull or a license change in the future. We know that we cannot assuage that anxiety with our words alone: trust is earned, it is not given.

But we do ask that you hold us accountable: to critique us if we misstep and to fork us if you must.

10. How was gitdot built?

We document major design decisions in the /designs folder.
We chronicle our progress and our thinking in the /weeks folder.

As engineers, we are painfully aware of our own inadequacies.
Building gitdot has made it obviously clear that there is much to learn and to improve still.
Yet, it is our hope that in some small way, these docs are our opportunity to give back.

11. Who built gitdot?

Two dudes in Brooklyn.

12. Why is it named gitdot?

🐐