+1
On Jul 22, 2025 at 4:05:00 PM, Mick Semb Wever wrote:
>
> +1
>
>
> On Mon, 21 Jul 2025 at 17:52, Joel Shepherd wrote:
>
>> Hi dev@ - I'd like to request voting for adoption of CEP-50:
>> Authentication Negotiation.
>>
>> Proposal:
>>
>> https://cwiki.apache.org/confluence/display/CASSANDRA/
On 7/23/2025 7:21 AM, Josh McKenzie wrote:
There anything in that README that we could/should promote to
https://cassandra.apache.org/_/development/testing.html?
There'd be some value in selectively referencing some of the tools in
there, or at least mentioning their existence.
Let me get
Thanks, Dave, for offering your help and support. We’re all set for now —
Alex has added me as a co-owner of the Meetup page. I’ll reach out if we
need assistance in any other areas.
Jaydeep
On Wed, Jul 23, 2025 at 10:56 AM Dave Herrington
wrote:
> Jaydeep/Alex,
>
> I'm located in the Bay Area
+1 to Patrick's proposal.
On Wed, Jul 23, 2025 at 12:37 PM Patrick McFadin wrote:
> I just did some review on all the case law around copywrite and AI code.
> So far, every claim has been dismissed. There are some other cases like
> NYTimes which have more merit and are proceeding.
>
> Which lea
Now seriously. Who would want to miss this meetup!??
On Wed, Jul 23, 2025 at 12:18 PM Josh McKenzie wrote:
> I'll start micro-dosing the poison now to build up immunity.
>
> There's still time.
>
> On Wed, Jul 23, 2025, at 2:53 PM, Patrick McFadin wrote:
>
> Fine Josh. No more arm wrestling. I h
I just did some review on all the case law around copywrite and AI code. So
far, every claim has been dismissed. There are some other cases like
NYTimes which have more merit and are proceeding.
Which leads me to the opinion that this is feeling like a premature
optimization. Somebody creating a P
Hello,
The world moved forward, this is a fact. At the same time, most of
people pushing their stuff to github, or other repository hosting
solutions, rarely populate license information, and do not provide
explicit patent rights.
I agree that forbidding specific tools sound ridiculous, however
I'll start micro-dosing the poison now to build up immunity.
There's still time.
On Wed, Jul 23, 2025, at 2:53 PM, Patrick McFadin wrote:
> Fine Josh. No more arm wrestling. I have a new game where we try to guess
> which cup of tea has the poison in it!
>
>
> On Wed, Jul 23, 2025 at 7:24 AM
+1
On Tue, Jul 22, 2025, at 5:26 AM, Štefan Miklošovič wrote:
> +1
>
> On Tue, Jul 22, 2025 at 5:03 AM Bernardo Botella
> wrote:
>> Proposing the test build of Cassandra Analytics 0.1.0 for release.
>>
>> sha1: 6e1d5257a8d6c910a42751475612145533ae3b1d
>> Git: https://github.com/apache/cassandr
According to the thread, the disclosure is for legal purposes. For example,
the patch is not produced by OpenAI's service. I think having the
discussion to clarify the AI usage in the projects is meaningful. I guess
many are hesitating because of the unclarity in the area.
> I don’t believe or agr
Fine Josh. No more arm wrestling. I have a new game where we try to guess
which cup of tea has the poison in it!
On Wed, Jul 23, 2025 at 7:24 AM Josh McKenzie wrote:
> I'll be there, and I hope if you are in the area, you don't miss this
> opportunity for us to connect.
>
> Do not arm wrestle P
This is starting to get ridiculous. Disclosure statements on exactly how a
problem was solved? What’s next? Time cards?
It’s time to accept the world as it is. AI is in the coding toolbox now
just like IDEs, linters and code formatters. Some may not like using them,
some may love using them. What
> David is disclosing it in the maillist and the GH page. Should the disclosure
> be persisted in the commit?
Someone asked me to update the ML, but I don’t believe or agree with us
assuming we should do this for every PR; personally storing this in the PR
description is fine to me as you are
That’s a great point. I’d say we can use the co-authored part of our commit
messages to disclose the actual AI that was used?
> On Jul 23, 2025, at 10:57 AM, Yifan Cai wrote:
>
> Curious, what are the good ways to disclose the information?
>
> > All of which comes back to: if people disclo
Jaydeep/Alex,
I'm located in the Bay Area and am happy to help out in any way needed with
the meetup coordination.
-Dave
On Tue, Jul 22, 2025 at 3:49 PM Jaydeep Chovatia
wrote:
> Sure, Alex.
> Let me know if somebody else living in the Bay Area wants to own it;
> otherwise, I am happy to own i
Curious, what are the good ways to disclose the information?
> All of which comes back to: if people disclose if they used AI, what
models, and whether they used the code or text the model wrote verbatim or
used it as a scaffolding and then heavily modified everything I think we'll
be in a pretty
Sent out this patch that was written 100% by Claude:
https://github.com/apache/cassandra/pull/4266
Claudes license doesn’t have issues with the current ASF policy as far as I can
tell. If you look at the patch it’s very clear there isn’t any copywriter
material (its glueing together C* classes
> I'll be there, and I hope if you are in the area, you don't miss this
> opportunity for us to connect.
Do not arm wrestle Patrick. Unless you like doing PT afterward.
I'll be there; have some things to present and chat about. :D
Looking forward to it!
On Tue, Jul 22, 2025, at 6:48 PM, Jaydee
There anything in that README that we could/should promote to
https://cassandra.apache.org/_/development/testing.html?
On Tue, Jul 22, 2025, at 8:04 PM, Joel Shepherd wrote:
> Ah, thanks: all kinds of good stuff in there.
>
> -- Joel.
>
> On 7/22/2025 1:45 PM, Mick Semb Wever wrote:
>>
>> try
That's a really good idea! I have updated the CEP to include this
duplicate_key_policy functionality and corresponding test scenarios.
On Tue, 22 Jul 2025 at 16:35, Patrick McFadin wrote:
> Another hit from the DevOps request backlog. I'm glad this has
> finally turned into something formal. Thi
20 matches
Mail list logo
