bradrydzewski

Gitness actually launched in 2012 under the name Drone, with a focus on continuous integration. So Gitness has a very strong, mature pipeline engine that is also very popular in the Gogs and Gitea community (Gitness is backward compatible with any Drone yaml). Of course, this is just our initial launch which is a very important milestone, but we have a lot of feature gaps and a lot of work to do to make our Code Hosting solution a more interesting replacement. Stay tuned.

Edit: if you have feature requests, let us know!

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

Yes. Dark mode is coming. Code Snippet management is a great suggestion and we will absolutely pick this up. Thanks for testing it out. Hit us up in our Slack channel if you have any future suggestions or if there is anything we can do to help.

Very possible. SourceHut is great and seems to be most popular with developers and open source teams (although I'm sure they also have corporate users too). We are more focused on companies and enterprises. These are different segments of the market with different needs. The former also tends to have higher user counts with lower average deal size, while the latter has lower user counts with very high average deal size.

With that being said, Gitness is a rebranding of Drone, which has 10,000+ active installations so I would say we are off to a pretty good start!

I see Gitness as the evolution of Drone. We are using the Drone pipeline engine and a ton of Drone code under the hood, but we are also adding Code hosting capabilities. And at some point, when you upgrade to the next major version of Drone, you will actually be upgrading to Gitness.

I should mentioned that we will never force you to host your code on Gitness. You will be able to use Gitness Pipelines with other code hosting providers, including Gitea.

I think the challenge with starting a new project is that it would result in Drone feeling completely abandoned because there would be zero investment going forward. We want to bring the community with us. I really do think Harness is breathing new life into the Drone project with this rebranding (12 full time developers and counting) and I am really excited to see where we are a year from now.

PS glad to hear you like Drone. I hope you will consider testing out Gitness at some point and letting us know what you think. It is still early days, but the team is making improvements daily. Hit us up in our Slack channel if there is anything we can do to help.

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.

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.

It is a portmanteau of Git and Harness

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!

I think this is a matter of perspective. I founded a company that sold b2b software and experimented with removing pricing from my website. The challenge is the cost to complete each sale was highly variable which made it difficult to advertise fixed pricing. Consider the following:

If the buyer is an enterprise they expect a discount. The buyer may require the seller to use a supplier management tool like Arriba which has a monthly subscription fee. The buyer may purchase through a reseller, in which case the reseller expects a percentage of the transaction. The buyer may require custom contracts which can cost thousands of dollars in legal fees. The buyer may require extensive audits, pages of questionnaires and more which can take significant time and resources to complete. The buyer may hold back payment for up to 180 days.

So from my perspective, the problem is not the seller, the problem here is the enterprise buyer. If the buyer was willing to purchase from a website, with a credit card, and accept standard terms and pricing without modification, you would probably see much more transparent pricing and encounter fewer "contact sales" buttons.

while on the topic of business focus, is Brex still in the restaurant business?

https://www.sfchronicle.com/food/article/Multibillion-dollar...

The purpose of this software is to allow remote management of sqlite databases using existing postgres GUI tools.

> Postlite is a network proxy to allow access to remote SQLite databases over the Postgres wire protocol. This allows GUI tools to be used on remote SQLite databases which can make administration easier.

The readme does not seem to advertise this software as being a drop-in replacement for Postgres by any means, although I can understand your frustration with database vendors that market their software as such. I suspect they used Postgres as the wire format because otherwise they would need to invent one from scratch, and then work with existing tools to integrate. Leveraging the Postgres wire form means they can integrate with existing GUI tools on day one, and seems to be a very pragmatic choice.

I believe copyright law in the U.S. is governed by federal statute and copyright infringement matters would be handled by a federal court.

Kyle is one of the authors of Polyform and the Polyform website specifically states that these licenses are not Open Source.

> PolyForm is not Open source or free software. There are plenty of existing open source licenses. PolyForm is not a substitute for them, but an alternative for those who want to license source code under limited rights.

Drone supports many different target runtimes, including running pipelines directly on the host similar to Jenkins. See https://docs.drone.io/installation/runners/

One-sided would imply that only one party benefits. You clearly benefit from being able to use and improve software, for free, for practically any purpose.

I respectfully disagree with the suggestion that this is immoral.

Sentry is granting you a license, for free, to do anything you want with the software except provide a commercial competitor to their hosted service. People using the software for free may still decide to contribute code. This is not a one-sided relationship here. Both parties are getting something of value.

I have been using and contributing and publishing open source software (and source available software) since 2004. The first time I heard of the OSI and OSD was in 2017. For years I thought open source simply meant the source code was public.

I would not be surprised if > 50% of the global developer population is unaware of the OSI or OSD. The fact that most public GitHub projects have no license certainly should have us questioning levels of awareness.

I do agree this project should change the language on the homepage, especially as they receive feedback in this thread. However, I think we should give people the benefit of the doubt before we assume they are acting in bad faith.

You might find it interesting that Stallman supports selling exceptions to the GPL (i.e. dual licensing). You can read more about it on the FSF blog [1] but the post ends with the following:

> I consider selling exceptions an acceptable thing for a company to do, and I will suggest it where appropriate as a way to get programs freed.

[1] https://www.fsf.org/blogs/rms/selling-exceptions

I recommend taking a look at the API Copyleft License https://github.com/kemitchell/api-copyleft-license/blob/mast...

Yes, it supports windows, macos, and linux. I expect it will also support bsd although I have not tested this yet. This should land in master some time this week.

Tekton [1] works in a similar manner where the pipeline stages define inputs, outputs and tasks. The great part about Tekton is it provides a set of building blocks that can be integrated into a larger system.

I hope to integrate Tekton into Drone [2] and allow individual projects to choose their pipeline execution engine. Projects can choose to start with a more basic engine, knowing they have the option to grow into something more powerful (and complex) when they need to.

[1] https://tekton.dev/ [2] https://github.com/drone/drone/issues/2680

> It only works with Docker containers

This will only be true for another week or two. We have devised a framework for alternate runtimes, including running pipelines directly on the host machine or in traditional virtual machines, that will be released end of week. Reference issue https://github.com/drone/drone/issues/2680

There was an interesting community-driven project to create a dashboard for Drone, see https://github.com/drone/drone-wall. I would love to see more like it.

Drone is working on support for Starlark, a python-inspired configuration language used by the Bazel Build system [1]. For complex pipelines, this should be more analogous to Jenkins scripting and may improve scaling Drone for larger projects (time will tell).

[1] https://github.com/bazelbuild/starlark

If you are building everything on the same machine you could get rid of the registry and watchtower, mount the host machine docker socket into your pipeline, and build and start the image on the host machine from inside your pipeline.

I use dockerhub/github/drone/watchtower to automatically publish images and update services. I use dockerhub and github to avoid self-hosting the registry and version control. I also have about a dozen servers (as opposed to single-server in your example). This works really well for me and does not feel patchy. Yes there are moving parts, but fewer moving parts than a full-blown orchestration system.

thanks for the response. I will add my name to the waitlist and look forward to discussing at a future date.

I really like the idea, and appreciate that there are people out there trying to solve this problem! I have struggled to financially support my open source projects through donations and support contracts, and ultimately decided on an open core model, which has yielded the most success to date. Moving to an open core model is challenging and building out a sales process and sales team can be a barrier for many developers. I was wondering if you have considered including something like reselling, for lack of a better word, in your offering. Having someone negotiate a variety of monetization options on behalf of the project, including selling licenses, would be very interesting. (note I acknowledge open core is not open source, and therefore may be contrary to the goals of this startup).

Have you considered submitting for OSI approval?

mongodb announced the Server Side Public License change less than 12 weeks ago. When you account for end of year and holidays, building a new product line and rolling it out in such a short period of time seems unlikely. I would guess this has been in the works for a while (although admittedly I could be overestimating engineering effort and underestimating amazon engineering talent).