potiuk commented on code in PR #60158: URL: https://github.com/apache/airflow/pull/60158#discussion_r2671342686
########## .github/PULL_REQUEST_TEMPLATE.md: ########## @@ -1,44 +1,37 @@ <!-- - Licensed to the Apache Software Foundation (ASF) under one - or more contributor license agreements. See the NOTICE file - distributed with this work for additional information - regarding copyright ownership. The ASF licenses this file - to you under the Apache License, Version 2.0 (the - "License"); you may not use this file except in compliance - with the License. You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, - software distributed under the License is distributed on an - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY - KIND, either express or implied. See the License for the - specific language governing permissions and limitations - under the License. - --> +Thank you for contributing! -<!-- -Thank you for contributing! Please make sure that your code changes -are covered with tests. And in case of new features or big changes -remember to adjust the documentation. +Please provide above a brief description of the changes made in this pull request. +Write a good git commit message following this guide: http://chris.beams.io/posts/git-commit/ + +Please make sure that your code changes are covered with tests. +And in case of new features or big changes remember to adjust the documentation. -Feel free to ping committers for the review! +Feel free to ping (in general) for the review if you do not see reaction for a few days +(72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: -closes: #ISSUE -related: #ISSUE +* closes: #ISSUE +* related: #ISSUE +--> + +## Was generative AI tooling used to co-author this PR? Review Comment: Actually - that was also quite deliberate. "Authoring" has a more broad meaning than "agentically adding the code" - even if you "ask" and use the suggestions of AI - AI is "co-author". Same as when in GitHub UI you suggested above, I might choose to commit your suggestion, which will make you co-author of this commit (and actually even adding automatically co-author in the commit message). Also this is the term used in https://www.apache.org/legal/generative-tooling.html where "authoring using generative AI tooling" is used. > When providing contributions authored using generative AI tooling, a recommended practice is for contributors to indicate the tooling used to create the contribution. This should be included as a token in the source control commit message, for example including the phrase “Generated-by: ”. This allows for future release tooling to be considered that pulls this content into a machine parsable Tooling-Provenance file. A bit of philosophical context (It's a very interesting subject and I am following and participating in discussions about it in ASF): I actually very much like "authoring" term - like for example Dag Authoring. This applies very broadly - anything that ends up in created code (in this case). For example using automated linting to create Dag is also somewhat "authoring" it with those tools. The big difference (and that also relates to @o-nikolas suggestion that we might be asked about IDEs) is that currently we are in a little bit of a legal vacuum - unlike automated liniting and IDE classic autocomplete (before AI) - is quite clearly non-copyrightable, there is a debate going on if the AI generated code is. And there is no clear answer. Some legal precedents already exists and courts generally dismiss claims that AI generated code (and music, and images and videos etc.) is copyrightable according to the current "copyright" law. This is something we deeply discuss in the ASF, but I think it's a bit early to have a definite answer, and my thinking - and a number of people in ASF think the same - that we (industry and humanity) will have to come up with a different kinds of laws for this - because "copyright" does not apply to it at all. We have to remember that copyright law is rather new (for humanity) and is really a "social agreement" invented to protect creators and when it was created, anything like Gen AI was not even imaginable. So "authoring" is a way to say - it was used to create it. And the only reason we expect it here (and why it was written like that in the guidelines) is precisely because the legal situation is not clear and we want to keep track of it just in case. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
