Re: [DISCUSSION] Cassandra's code style and source code analysis

2023-01-27 Thread Claude Warren, Jr via dev
Turn it on at warning (or lower) level now, so people have some idea of the size of change to their current code. On Wed, Jan 25, 2023 at 12:05 PM Miklosovic, Stefan < stefan.mikloso...@netapp.com> wrote: > Thank you Maxim for doing this. > > It is nice to see this effort materialized in a PR. >

Re: [ANNOUNCE] Evolving governance in the Cassandra Ecosystem

2023-01-27 Thread Josh McKenzie
I'm told my email came through with a white background and gray font. Apologies for that; contortions between editors and trying to get my email client to format consistently after copy/paste led to some kind of pathologically bad case. Also: you should be using a dark background on your browse

Re: Merging CEP-15 to trunk

2023-01-27 Thread Henrik Ingo
While the substance of the review discussion has moved to Jira, I wanted to come back here to clarify one thing: I've learned that when I have defended the need (or right, if appealing to the Governance texts...) for contributors to be able to review a feature branch at the time it is merged to tr

Re: [ANNOUNCE] Evolving governance in the Cassandra Ecosystem

2023-01-27 Thread Francisco Guerrero
Great news! I'm very happy to see these changes coming soon. Thanks to everyone involved in this work. On 2023/01/26 21:21:01 Josh McKenzie wrote: > The Cassandra PMC is pleased to announce that we're evolving our governance > procedures to better foster subprojects under the Cassandra Ecosystem

Re: Merging CEP-15 to trunk

2023-01-27 Thread David Capwell
> I've learned that when I have defended the need (or right, if appealing to > the Governance texts...) for contributors to be able to review a feature > branch at the time it is merged to trunk - which for Accord is now - that a > common reaction to this is that doing a review of Accord now mig

Re: Merging CEP-15 to trunk

2023-01-27 Thread Josh McKenzie
> I know that many of us review code after it has been merged, and what we have > been doing is filing follow up bugs/improvement requests as new work. I think this is key. The code on the feature branch matches the same bar of quality / process that's on trunk, and it's trivially easy to checkou

Re: Merging CEP-15 to trunk

2023-01-27 Thread Benedict
I'm realizing in retrospect this leaves ambiguityAnother misreading at least of the intent of these clauses, is that they were to ensure that concerns about a design and approach are listened to, and addressed to the satisfaction of interested parties. It was essentially codifying the project’s lon

Apache Cassandra Publicity & Marketing Group - Cassandra Summit Asks

2023-01-27 Thread Molly Monroy
Hello All: I will be supporting the publicity & marketing working group along with my colleagues at Constantia, which partners with Cassandra for publicity and marketing. For those of you I haven't met yet, I look forward to working with you! For our first order of business for this group ... We