Re: Fwd: [CI] What are the troubles projects face with CI and Infra
Another thing worth mentioning is the overhead with providing, setting up, and managing infrastructure. While donations of servers/VM’s works to some extent, it’s a somewhat archaic donation policy – and this whole structure of CI gives both the ASF and the C* project very limited choices. From my perspective it would be much more suitable for the C* project to receive financial or credit based donations, on which we could utilise against whatever CI/CD we desired. This would open up modern options for CI and not limit us to just ASF-ran Jenkins. I’m sure this would be much more suitable for many smaller organisations, with possible tax benefits as well, rather than providing infrastructure (which lets face it, is rarely bare metal servers these days) that they have to maintain. For example, It’d be ideal if there was a C* CircleCI account (or deployment) that the project could use that could be funded by the community, rather than the big backers being the only ones able to run the tests effectively (and thus everyone relying on them paying for and doing it for them). On 2020/02/02 21:51:54, Nate McCall wrote: > Hi folks, > The board is looking for feedback on CI infrastructure. I'm happy to take > some (constructive) comments back. (Shuler, Mick and David Capwell > specifically as folks who've most recently wrestled with this a fair bit). > > Thanks, > -Nate > > -- Forwarded message - > From: Dave Fisher > Date: Mon, Feb 3, 2020 at 8:58 AM > Subject: [CI] What are the troubles projects face with CI and Infra > To: Apache Board > > > Hi - > > It has come to the attention of the board through looking at past board > reports that some projects are having problems with CI infrastructure. > > Are there still troubles and what are they? > > Regards, > Dave > Sent from Mail for Windows 10
Re: Moving forward towards our best release yet
unsubscribe On Thu, 2 Jul 2020 at 13:20, Jeremy Hanna wrote: > I've been in the Cassandra community for about 10 years now and I've seen > a lot of ups and downs. I care deeply about both the project and the > people interacting on the project personally. I consider many of you to be > good friends. > > Regardless of the history that's caused some friction on recent discussion > threads, I hope we can all see past the "us versus them" towards shipping > something excellent and building momentum. > > I would just ask - please assume that everyone wants the project to > succeed - to build the best, most stable, most scalable, most developer and > operationally friendly database out there. Please know that while you > personally may have seen X clusters in your work with Y nodes with Z > challenges, you're in good company - we all have. Let's assume that > everyone has a unique contribution based on battle scars and triumphs. As > we listen to each other with this in mind, I think we can move forward more > effectively. There are so many complementary efforts that can help make > things more stable, reproduce issues and test for regressions now. As we > get into the final stages of the 4.0 release cycle, I think we can bring > all of this to bear for the best release we've ever had. > > We all have different viewpoints but please let's assume the best in > others and communicate constructively. We all have things to contribute - > large or small - and it's great to see renewed interest with new > contributors. With all of the energy leading up to the release, I think > we're seeing a glimpse of what we can do as a revitalized project and > community and this is just the beginning. > > Thanks for all you do, > > Jeremy > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
