Hi Christian, sepehr, Yuya and Osama,

We have a AI policy for Github comments already [1]. If you want
to expand it to e-mails and PRs, feel free to open a policy RFC.


Personally, I am okay with AIGC. Fundamentally AI is a tool, and
clearly a useful one. In this thread, I think you treat "use AI or not"
in comments as a "Proof of work" in this era.  In most cases, people
using AI to generate text seems to put less effort in it, that's true,
but I don't agree with some of the "progressive" AI policy you've
mentioned in other projects. As a maintainer of the intl extension,
I'd focus more on the code quality itself rather than whether it's
AI-generated code or comments. I frankly don't agree with the
proposal to ban AI in the php internals.


That being said, I feel disgust to communicate with soul-less
contributors who entirely use AI without any critical thinking.
However, it depends. If one can use AI to generate good code
and idea, I am glad to work with these people. I don't see the
benefit to completely ban AIGC in the project.


Also to sepehr: Thank you for your interest in the intl extension!
To get you started: in the extension, some constant can be enums.
And, I would be in favor of appropriate namespaces to avoid conflicts
in the extension's class that make things clearer. Maybe that is a good
RFC idea in 8.7 that needs someone to work on. Also, it is still in
progress to fill in the little blanks between php APIs and ICU APIs. It
might to a good way to start if you want to add new functions/methods.
Not to mention the error state stuff in the extension is, frankly, bad, in
my opinion, and could be optimized since it has caused a lot of very
stupid bugs and make my life harder :( There are still bugs and PRs on
Github you can help with, the list goes on and on and on...


There are tons of things you can do :) This goes to everyone who want to
contribute to the extension.


Cheers,
Weilin Du, [email protected]


[1]: 
https://github.com/php/php-src/blob/master/CONTRIBUTING.md#llm-usage-in-github-comments 

Reply via email to