Willy, Am 22.12.20 um 19:51 schrieb Willy Tarreau: >> Open Source projects can get additional top-ups, but not recurring, so >> one would need to send an email every few weeks whenever the minutes run >> out. >> >> And also to qualify for the Open Source credits *not a single* paid >> employee may work on the Open Source project. > > This is non-sensical. If they can come up with a *single* example of > long-term successful opensource project which is not at least indirectly > backed by either a company or a foundation, I'd be glad to know about it.
Yeah exactly. I don't even know what would happen with their policy when someone sends a single patch while on company time, but otherwise does not regularly contribute. Is your Open Source project backed by a company if you accept that patch? > The truth is, most opensource projects start when developers are students > with plenty of time and willingness to implement better versions of existing > stuff, and once they start to work and to get a real life, either the project > dies (hence why 99.9% of projects don't go past 3 years) or they present an > interest for an employer and the developer continues to be allowed to work > on it. Sadly it just proves that Travis has no idea how opensource works, > and while we've always been cautious not to abuse their infrastructure to > remain good citizens, I doubt they'll recover well from kicking everyone > off of their systems :-/ I have a few smallish open source projects that I maintain in my personal time (e.g. https://github.com/TimWolla/haproxy-auth-request), but I would not even use Travis for those. I want to do useful stuff (e.g. adding a feature) and not waste time sending emails begging someone for more build minutes until I can continue working on it. I also never would suggest starting to use paid Travis to my employer when I have GitHub Actions experience from my personal projects and the employer could just pay for GitHub Actions instead and already have the necessary expertise is already there. >> So: Travis is effectively dead for HAProxy, unless Travis CI management >> changes their minds. > > I pinged them when you sent me the announcement, I never even received a > reply. I suspect a change of management in the company, or that they might > be in serious financial trouble and have to urgently cut costs everywhere > to save what can still be saved. In any case it's sad, as it's always sad > to see a significant actor in the opensource ecosystem disappear. A bit of both I think. They were acquired in early 2019 (see https://en.wikipedia.org/wiki/Travis_CI#Company) and they also reported that many users would abuse Travis CI builds to mine Bitcoins until the job timed out after 50 minutes. You really can't have nice things. > Removal patch applied by the way. Thanks! Best regards Tim Düsterhus
