+1 with taking it to legal
As anyone else I enjoy speculating about legal stuff and I think for jars you
probably need possible deniability aka no paper trail that we knowingly... but
that horse is out of the barn. So really interested in what legal says
If you can stomach non Java here is
> For my understanding, isn’t it gonna be an issue to be copyrighted also
to a single person? For the same reasons?
This was partly why I asked. I did a random check of libraries that are
definite dependencies (netty, guava) and both contain author copyrights.
On Fri, 22 Sept 2023, 16:01
For my understanding, isn’t it gonna be an issue to be copyrighted also to
a single person? For the same reasons?
On Fri, 22 Sep 2023 at 7:59, Mick Semb Wever wrote:
>
>
> Just for my understanding on this. Is the issue that the code has a
>> copyright header on it or that it is copyright to a
> I highly doubt liability works like that in all jurisdictions
That's a fantastic point. When speculating there, I overlooked the fact that
there are literally dozens of legal jurisdictions in which this project is used
and the foundation operates.
As a PMC let's take this to legal.
On Fri,
To do that, the cassandra PMC can open a legal JIRA and ask for a (durable,
concrete) opinion.
On Fri, Sep 22, 2023 at 5:59 AM Benedict wrote:
>
>1. my understanding is that with the former the liability rests on the
>provider of the lib to ensure it's in compliance with their claims
I have just created CASSANDRA-18876 for this. I'll post a patch very soon.
On Wed, 20 Sept 2023 at 19:41, David Capwell wrote:
> I don’t think we can readily migrate old types away from this however,
> without breaking backwards compatibility.
>
>
> Given that java driver has a different
my understanding is that with the former the liability rests on the provider of the lib to ensure it's in compliance with their claims to copyrightI highly doubt liability works like that in all jurisdictions, even if it might in some. I can even think of some historic cases related to Linux where
This Gen AI generated code use thread should probably be its own mailing list DISCUSS thread? It applies to all source code we take in, and accept copyright assignment of, not to jars we depend on and not only to vector related code contributions.On Sep 22, 2023, at 7:29 AM, Josh McKenzie
So if we're going to chat about GenAI on this thread here, 2 things:
1. A dependency we pull in != a code contribution (I am not a lawyer but my
understanding is that with the former the liability rests on the provider of
the lib to ensure it's in compliance with their claims to copyright and
My reading is quite different, in fact it is quite explicit that e.g. ChatGPT is forbidden from use, whereas AWS CodeWhisperer may be permitted depending on the attribution.I assume you are reading clause 2.1, but this requires that work "would not be [copyrightable] even if produced by a human”
On Thu, 21 Sept 2023 at 10:41, Benedict wrote:
> At some point we have to discuss this, and here’s as good a place as any.
> There’s a great news article published talking about how generative AI was
> used to assist in developing the new vector search feature, which is itself
> really cool.
Just for my understanding on this. Is the issue that the code has a
> copyright header on it or that it is copyright to a corporate entity?
>
The potential issue here is about dependence upon one vendor (or commercial
actor).
If the project is not usable without a specific piece of work
Just for my understanding on this. Is the issue that the code has a
copyright header on it or that it is copyright to a corporate entity?
On Fri, 22 Sept 2023 at 10:11, Mick Semb Wever wrote:
> Especially for an optional feature with clear alternative implementations,
>> this doesn't bother me
>
> Especially for an optional feature with clear alternative implementations,
> this doesn't bother me at all. It's well within ASF policy to include
> permissively licensed code copyrighted by other people or entities.
>
We should be conscious of the problem if this was a crucial (and
14 matches
Mail list logo