alamb commented on PR #2788:
URL: 
https://github.com/apache/datafusion-sqlparser-rs/pull/2788#issuecomment-6589422162

   Thank you for the contribution. The change may well be correct, but I am 
closing this PR under the DataFusion [AI 
policy](https://datafusion.apache.org/contributor-guide/ai-policy.html#what-is-an-ai-dump-and-why-it-is-not-helpful),
 which also applies to sqlparser-rs.
   
   Maintainer review time is the scarcest resource in this project. This 
account has opened more than 30 PRs across many repositories in the last month, 
which looks like GitHub "merge-maxxing" (collecting merged PRs) rather than 
work on a project the author uses. Several similar PRs have been closed 
elsewhere (for example 
[boa-dev/temporal#760](https://github.com/boa-dev/temporal/pull/760), 
[OSGeo/grass#8126](https://github.com/OSGeo/grass/pull/8126), 
[OSGeo/grass#8127](https://github.com/OSGeo/grass/pull/8127), 
[python/cpython#158491](https://github.com/python/cpython/pull/158491) and 
[wagtail/wagtail#14670](https://github.com/wagtail/wagtail/pull/14670)), and 
the only review on this PR came from another account whose PRs we have closed 
as AI-generated. That suggests the changes aren't coming from someone who uses 
sqlparser-rs, and that no human will be around to discuss review feedback and 
maintain the code. Reviewing PRs like this costs us more time than it saves.
   
   If you do use sqlparser-rs and this fix matters to you, please pick the one 
change you care most about. Then open a focused PR with a short description in 
your own words, one you have reviewed and understand, and we'd be happy to help 
with review.
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to