Hej @opengeek,
thanks for posting this! I have been waiting to see what others think, including the “big ones” in the MODX community. Sadly, there has been no feedback from @markh, @hyponym, @muzzwood, @sterc, @jako and so on.
I can see some benefits of using AI for coding. I also have in mind where the models were trained and the deep impact it has on emissions. So I’m undecided about using it. But this is my decision as an individual developer.
For MODX, there is a large community missing, so AI could help to keep the project alive. Having made a pro/con list, I think we should use AI until the community grows again or until we can release the next version and cut the old codes (ExtJS, etc.) that make MODX a really modern CMS.
So, let’s take action on your ideas!
Large amount of PRs
I think it’s a good idea to add some notes to the documentation. This could start as a PR and be refined together inside the PR. It could be like the PR for the readme from last week.
The PRs from @ibochkarev are a mix of features and bug fixes. Bug fixes should go directly as a PR on GitHub. Features should be discussed in the MODX forum. There should be no GitHub discussions to have a single channel for communicating with technical and non-technical users. However, posting it directly to GitHub is an additional step that may confuse non-technical users.
There should be a community manager who keeps an eye on this (bearing in mind the open collective budget):
- Is there a new PR? Check whether it is small, medium or large. Add a tag for the release. For example, small could be
3.2.1, medium could be3.3, and large could be3.4. These tags can be modified later. However, group them first to make it clearer and lower the review pressure. - Is there a new topic with a feature? Discuss it with the community. Then let the community vote on it and plan for a release.
- Is there a new GitHub issue/discussion with a feature? Notify the author to add it to the forum.
This will increase transparency and bring us a step closer to creating a roadmap that we can use for pitching MODX too.
When opening a PR, there should also be a note about using AI. Here is a blueprint for this: Add multiselect field type with SuperBoxSelect and configurable separator by jenswittmann · Pull Request #218 · modmore/ClientConfig · GitHub .
Is this something you as a contributor would be amenable to, regardless if you used AI-assistance or not?
So at all. Let’s start using AI for anyone who wants it. First, we need a clear roadmap and a discussion of features, followed by a review of the hybrid process (with or without AI review/writing).