Of course, Sam and the team are the undisputed authority and can correct me if I’m wrong, but after much experimentation on my part and happy to give something back in return, I’ve learned over the past few months that Discourse Vibe and good use of the harness is what is suggested and by far the ideal situation to start with.
It is also possible to work with certain tests on Github or even using Discourse Container, but the development capacity is limited, especially for those less experienced like in my case.
It is possible to ‘vibe’ code for Discourse using AI and one just has to verify or delegate the final verification before presenting the work done or using it on production.
For my part, I am not technically qualified to review code, but I am enough to direct functionalities, how and where to adapt them, and ask about what specifically generate or polish so I imagine someone will come and openly contribute to the security and reliability (human review always) of the code so that it can be used by the entire community. Not only in Meta but Discourse in general. It has always been my goal, from my initial prompt.
Yesterday I read this topic and was surprised by how everything has evolved: How hard would it be for non programmers to be able to use the Discourse AI - AI bot to help them create plugins and/or themes
Years ago I thought I would not have been able to even direct an AI to make the code for me. And today, with the caveats and legitimate controversy that exists regarding this, it is a reality.