81–89 of 89 posts
Interestingly it looks like this is partly a fork of Gitea (or at least, incorporates large amounts of code from Gitea): https://github.com/harness/gitness/pull/3364/files#diff-4673...
Interestingly it looks like this is partly a fork of Gitea (or at least, incorporates large amounts of code from Gitea): https://github.com/harness/gitness/pull/3364/files#diff-4673...
It is largely based on the existing Drone repository, but for Git capabilities we used the Gitea fork of https://github.com/gogs/git-module
Earlier quoted context omitted.
This is probably my fault. Internally at Harness I have been hyping this launch as a "once in a decade" event. That unfortunately got translated into "first in a decade" when it hit the press. I do think the launch of a new, major open source Source Control system with kind of investment (12 full time engineers and counting) is a rare event, but I do wish it was worded differently. Nothing we can do about it now!
How does Gitness differ from already existing open source alternatives, such as Gitlab, Gitea, Gogs, Forgejo, Codeberg, Gitweb?
Edit: if you have feature requests, let us know!
Earlier quoted context omitted.
At this point Codeberg is clearly distinct from Gitea and is more thoroughly open-source in its nature than anything Harness is going to bring out, but yes, you could combine it with Forgejo if that feels more fair.
At this point Codeberg is running Forgejo not Gitea.
Earlier quoted context omitted.
Gitness is a continuation of Drone: they incorporated it in one big PR [0]. Cynically, when coupled with the CTA to star on GitHub, it feels like they did it this way to preserve the star and fork counts. [0] https://github.com/harness/gitness/pull/3364/
Nothing cynical about that statement. We definitely want to preserve the star counts! But as the founder of Drone, and Head of Product for Gitness, I see Gitness as the next major version of Drone. Gitness is built on the Drone pipeline engine and uses significant amounts of Drone code. And in the coming months, when you upgrade to the latest version of Drone you will get Gitness. So to me, they are one and the same.
For example, the press release entitled "Harness Releases Gitness" is clearly describing the release of a new Harness product, not a rebranding of Drone [0]. And your README doesn't say anything like "Gitness is Drone 3.0", it says it's "powered by Drone".
You also didn't merge in a branch that built Gitness on top of Drone. Instead there's one commit that removes every single line of Drone code [1] and then another one that adds all of Gitness [2]. There's no continuity in the history between Drone and Gitness; Gitness effectively originates in one big "Initial commit" that just happens to be in the same GitHub repo as Drone used to be.
Two thirds of those stars were earned before Harness even acquired Drone [3], and it feels weird to me to see them used to push Harness's strategic move into Git hosting, even if that move is led by Drone's founder.
[0] https://www.harness.io/blog/harness-releases-gitness-open-so...
[1] https://github.com/harness/gitness/commit/7ab205375f34ab3850...
[2] https://github.com/harness/gitness/commit/e0aa6cb81ae73c0877...
Earlier quoted context omitted.
Gitness is a continuation of Drone: they incorporated it in one big PR [0]. Cynically, when coupled with the CTA to star on GitHub, it feels like they did it this way to preserve the star and fork counts. [0] https://github.com/harness/gitness/pull/3364/
Nothing cynical about that statement. We definitely want to preserve the star counts! But as the founder of Drone, and Head of Product for Gitness, I see Gitness as the next major version of Drone. Gitness is built on the Drone pipeline engine and uses significant amounts of Drone code. And in the coming months, when you upgrade to the latest version of Drone you will get Gitness. So to me, they are one and the same.
You don't see how that's a bit ridiculous?
https://github.com/drone/drone redirects to harness/gitness too, leaving the entire https://github.com/drone organization without its major repo. Not to mention, again, that all GitHub links on https://www.drone.io/ are now 404.
How compatible have Drone CI and it's open-source fork Woodpecker? I'm curious whether one might expect any kind of engine swap to work.
I can't find any git repos on gitness.com, where are they?
I can't find any git repos on gitness.com, where are they?
We have not launched our saas version yet. Our first launch focused on the open source, self hosted version. Saas version will be coming soon. Please stay tuned.
https://www.softwareheritage.org/ https://wiki.archiveteam.org/index.php/ArchiveBot