This is a way of working aspect of triaging. It belongs under the above linked bug triaging docs, not here. - My idea of "Contributing guide > Getting started" is that it should give a high-level idea of the kinds contribution and direct interested people to the relevant parts of the documentation. Specific information on how (not) to do things should be in those parts of the documentation e.g. bug triaging, not on the overview page.

I'll move it but I put it here b/c it's similar to the "no claiming" guidance that we have under "find an issue" https://matplotlib.org/devdocs/devel/contribute.html#work-on-an-issue

Which should I move that too?

My first impulse was: This belongs in https://matplotlib.org/devdocs/devel/triage.html. But considering the definition of triage actions on that site, replying with a solution is beyond triaging. Triaging only makes sure the issue is well laid out and sorted. It does not solve it (except for invalid or duplicate issues). Therefore, I don't see that people will respond with AI as part of triaging. To make life simple here, I claim it's out of scope for the PR and we can leave that section out.

In as separate PR, you could add something like "Proposing solutions" to the https://matplotlib.org/devdocs/devel/triage.html. It should be made clear that

• it's optional (a triager may add it if they already exactly know how to solve this)
• proposals / recommendations should be well considered and well laid out. If you are not sure, better leave the response to somebody else. This also includes auto-generated AI responses are not acceptable.

To make life simple here, I claim it's out of scope for the PR and we can leave that section out.

😭 that section was the whole motivation for this PR, but at least spinning it out into a new PR means this one no longer has to wait on the consensus on #28335

Also, separately I think "propose a solution" is required when somebody wants to close an issue claiming it's solved.

With my non-native English, I feel "helping out" is not that welcoming. I read it as "We have a deficiency. Can you temporarily take over a task that we currently cannot fulfill".

I suggest either

or

But you know the language better, so please decide whether to keep as is or change.

But you know the language better, so please decide whether to keep as is or change.

I'll change it because your helpful review told me how what I wrote is being read & that it's not conveying what I wanted it to.

Also changing it to

Our triage process is discussed in detail in :ref:bug_triaging

which I think ties in really well w/ @rcomer's suggestion of

If you have any questions about the process, please reach out on the :ref:`contributor_incubator

These stylings seem to make the cards less responsive to mouse-over. There's only a minimal size/layout change:
https://output.circle-artifacts.com/output/job/5b25daa3-7646-458d-9b4d-a2b5ab7702fb/artifacts/0/doc/build/html/devel/index.html

Previously, at least the small frame changed to purple, indicating a link.
https://matplotlib.org/devdocs/devel/index.html

Will change back but that seems like a pydata-sphinx-issue maybe :/