• "fork it and maintain it yourself"
• "if more people learned to code everytime someone complained about AI"
• "(code, bug reports, q&a, community engagement)"

That's three times that you said something about how people could "help". One of those three times held content other than code. It was parenthetical. And even there the first item was "code".

None of them were "writing documentation", incidentally.

So yeah, you totally didn't mean "code it yourself" at all. You genuinely meant you really want people to participate in ways that aren't code. I believe you.

Now, sarcasm aside, let's look at the process of "getting involved" in most software projects.

1. You need to learn this thing called "Git". Something that was apparently named after the person who designed its user interface because HOLY FUCKING RAURAVA is that about as user-hostile as it gets!
2. You need to sign up on some Microsoft piece of shit web site for the privilege of using this god-awful pile of festering sores you were forced to learn.
3. You finally post your bug report.

From this point onward one or more of these things traditionally happens:

• You get scolded for not following some format CLEARLY SPECIFIED in this document buried somewhere in the software's source code. (Never mind that on top of that, the "clear specification" was written by someone who has the communication abilities of an incontinent baboon with severe tremens smashing on a broken keyboard.)
• Your bug report sits on the queue forever, never commented on, never engaged with, and never fixed.
• Just like the previous one, but instead a bot comes in and closes down the bug report because "it may have already been fixed". (I technically have a bug report in on Open-now-LibreOffice that's outstanding for well over 15 years now. For the first three years, like clockwork, a bot would come in, close the report, saying "resubmit if it's still a problem". After three years I gave up. The bug still exists.)
• You somehow attract the attention of someone with your bug report and instead of asking for more information, for testing, etc. you're treated like an ignoramus, asked insulting questions, given huge impractical workarounds, and all other kinds of such things that don't actually fix the bug.
• You get "works on my machine" and the bug gets closed.

Oh, and sometimes you might actually see a bug get fixed.

Some communities are better than others over this. This is why there are some communities I actually do contribute to. ("...you're making an ass of yourself by assuming things about people you don't know.") But in general? The F/OSS community is one of the worst communities to work with. If you're not a coder you're treated like an irritant. A second-class human being. Worthless.

And then the F/OSS community wonders why they're not getting non-coder contributions...

As an aside:

You don't mind using their work, don't want to contribute to cause you don't want to learn to code

And here, incidentally, you go again, focusing on code even while scolding me for purportedly not contributing bug reports or otherwise. Because you're...

making an ass of yourself by assuming things about people you don't know.

How funny. I can't imagine why people don't want to associate with F/OSS communities in the slightest.