Our great sponsors
-
gitness
Gitness is an Open Source developer platform with Source Control management, Continuous Integration and Continuous Delivery.
-
Gitea
Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
drone
Discontinued Gitness is an Open Source developer platform with Source Control management, Continuous Integration and Continuous Delivery. [Moved to: https://github.com/harness/gitness]
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
I get that you feel that they're the same, and that makes sense since you founded both projects. But what is publicly visible communicates something very different.
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].
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, 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...
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
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/
I went to check on this, and it seems that https://github.com/harness/drone redirects to harness/gitness. I'm now very confused.
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