[nfc] update CONTRIBUTING.md to add basic LLM policy

[silverweed]

This Pull request:

Adds a section about LLM usage to CONTRIBUTING.md. It is not meant as a fully-fledged "AI policy" but just some basic common-sense guidelines that are nonetheless good to spell out.

Also adds a section about branch names, since opening a PR with a branch named master conflicts with our CI.

[ferdymercury]

Thanks!
Maybe also mention that copy pasting could lead to copyright infringement eg if LLM is copying verbatim from a GPL project into LGPL

[github-actions]

Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 3771838.

♻️ This comment has been updated with latest results.

[guitargeek]

Very nice, I think this is well-written and captures the essential etiquette!

Going further, we might spell out precisely what it means "to disclose whether the proposed changes (code or otherwise) were automatically generated", maybe with templates for such disclosures that can be added to commit messages and PR descriptions.

[dpiparo]

Thanks for this initiative. Before merging, even if I do not see huge hurdles ahead, I was thinking to discuss this a bit broadly within the core developers.

[vepadulano]

Thanks! A couple of minor suggestions from my side

[vepadulano]

Suggested change

	> For compatibility with our CI, your should create your PR with a **branch name different from `master`**.
	> For compatibility with our CI, you should create your PR with a **branch name different from `master`**.

[vepadulano]

I don't know if this is a term already being used elsewhere, but to be more general we could think about calling it "AI-assisted coding disclosure".

[hageboeck]

Is "parroting" a universally understood term?

Suggested change

	Likewise, PR comments and any sort of engagement with other contributors must not be parroting LLMs or chatbots.
	Likewise, PR comments and any sort of engagement with other contributors must not be a simple copy of an LLM's or chatbot's output.