Re: [DISCUSS] Add JVector as a dependency for CEP-30

[Benedict]

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” which is clearly not the case for most code. I suspect most generated code is forbidden in practice. Either way, the portions of any contribution produced by the code assistant must be included in a separate commit with the tooling used clearly marked in the commit, including any source attribution. This is likely a challenging task to undertake retrospectively, and we may need advice on how to proceed unless there is an audit trail of some kind that can be followed to ensure this is done accurately - particularly since multiple generative code tools appear to have been used in the production of this work. As I said, an annoying topic. On 22 Sep 2023, at 13:06, Mick Semb Wever <m...@apache.org> wrote:  On Thu, 21 Sept 2023 at 10:41, Benedict <bened...@apache.org> 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. Unfortunately it *sounds* like it runs afoul of the ASF legal policy on use for contributions to the project. This proposal is to include a dependency, but I’m not sure if that avoids the issue, and I’m equally uncertain how much this issue is isolated to the dependency (or affects it at all?) Anyway, this is an annoying discussion we need to have at some point, so raising it here now so we can figure it out. [1] https://thenewstack.io/how-ai-helped-us-add-vector-search-to-cassandra-in-6-weeks/ [2] https://www.apache.org/legal/generative-tooling.html My reading of the ASF's GenAI policy is that any generated work in the jvector library (and cep-30 ?) are not copyrightable, and that makes them ok for us to include. If there was a trace to copyrighted work, or the tooling imposed a copyright or restrictions, we would then have to take considerations.