Perhaps it’s a mirror just to try to draw people in? If you wanted to start a new social network you would market the hell out of it on Facebook so

I assume that they used GitHub during the development of Gitness.

It would be a bit risky to build your new git competitor inside itself, surely?

It's also kinda a hallmark of a mature computer anything to use itself in some way.

You bootstrap your compiler using another until you can self compile. You write a build tool plugin which uses an older version of itself to enhance its own build. Intel probably uses intel chips to design future intel chips. It happens all the time and aesthetically computer nerds are drawn to this type of beauty.

From elsewhere in the thread:

> We have been using Gitness to develop Gitness for the last 6 months. We do mirror on GitHub as a backup. But we also want to meet the community where they exist today, which is GitHub.

We have been using Gitness to develop Gitness for the last 6 months. We do mirror on GitHub as a backup. But we also want to meet the community where they exist today, which is GitHub.

If you don't mind me asking since you're here: will you be implementing ForgeFed in Gitness [0]? My sense is that federation is our best hope for breaking GitHub's network effects, and I'd love to see more projects like yours join the protocol.

[0] https://forgefed.org/

Thank you for the suggestion. We will look into it.

Could you provide some sort of status report about what Gitness actually is? According to the Git repo it looks like it started Feb 2, 2014, and Brad Rydzewski did the vast majority of the work on the project (e.g., 100x more than anybody else), and is still involved now. I downloaded it and tried it out (which is VERY easy to do), and the actual software seems to be a Typescript frontend and Go backend, with Monaco for a code editor, and nice diff view. I tried importing a very large repository, and it took a while, but did fully work, and browsing the repo after import was fast. It's Apache-2.0 licensed (thanks!). Was it open source from the beginning?

Gitness brings code hosting and pipeline execution together. It builds on top of the Drone continuous integration system, which Harness acquired. Brad was directly involved, but this time he had the help of 12 full time developers

Do you do code reviews during development?

I ran it locally and couldn't find my way to go from a conversation to its code context. Nothing is clickable. Screenshot: https://imgur.com/a/kk8wLIK

Thank you for the feedback. We are working on addressing this soon.

Reminds of the GitHub issue for hosting Gitea on Gitea, it's... a read to be sure: https://github.com/go-gitea/gitea/issues/1029

I run the Gitness Project at Harness (also Founded Drone, on which this is based). It was mentioned by another Harness employee, but we have been dogfooding Gitness internally for the past 6 months. The project is entirely self-hosted at this point.

There was a lot of discussion internally about what message it would send if we also published the source code on GitHub. I was very adamant that we need to host on GitHub because this is where Open Source collaboration happens today, and we need to meet developers where they are today.

No shame here.

It is important to remember that Gitea is a very popular project and is a success by any measure with tens of thousands of installs, and they host on GitHub. I don't think that detracts from how awesome their product is. GitLab also hosted on GitHub in the early days to grow their community.

I definitely hope that one day, developers will love Gitness as much as they love GitHub, and they will choose Gitness to host their Open Source communities. But that will take a lot of time and a lot of work. We are here for it, but today is just a humble day 1 launch. We have years of work ahead of us.