Find a new maintainer

[Chi-teck]

Drupal Code Generator turned 10 years, marking a significant milestone. Unfortunately, I don't have enough time to properly maintain it these days, as I need to focus on other projects, both commercial and open source.

Requirements for the new maintainer:

1. Extensive experience in Drupal development.
2. Previous contributions to this project (desirable).
3. Willingness to dedicate significant time to its maintenance.

[weitzman]

Wow, its been 10 great years. Drush users have benefitted so much from DCG. Thanks so much for your service.

[PierrePaul]

That's awesome and sad at the same time. If I can be of any help, let me know!

[Chi-teck]

Hi @chx. You were just granted access to this project. Feel free to commit whatever you think is appropriate.

Thank you!

[weitzman]

Thanks @chx and @Chi-teck. What a fantastic outcome!

[harivansh0]

Hi @Chi-teck , I’d be glad to join as a co-maintainer alongside @chx. I can contribute around 4 to 5 hours per week—would that be sufficient? I haven’t contributed to this project before, but I find it extremely useful and would love to get involved.

[Chi-teck]

Hi @harivansh0, at this moment @chx is the maintainer of this project. So it's up to him adding new co-maintainers. I am thinking of transferring project ownership (need to figure out how to do it on GitHub).

For now you can contribute through PRs.

Thanks.

[harivansh0]

Sure
Hi @chx, I can contribute around 4 to 5 hours per week. Let me know if there's anything I can assist with. I also have a few feature requests and improvement suggestions that I’ll be submitting as new feature issues soon.

[Chi-teck]

JS tests have high maintenance cost. They require complicated testing infrastructure and tend to fail more often then other. For instance Chrome 134 broke tests in all my projects (teamcapybara/capybara#2800). The tests you have removed actually were not for JavaScript. There were for fields, widgets and formatters because Drupal heavily relies on ajax in Field UI. I could not find a way to deal with ajax forms in Drupal functional tests. BTW it was possible in Drupal 7 simlytests.

For the reference almost all tests in Date Point module are written using WebDriver even though the module itself does not have any JavaScript to test. That's not because I wanted to test Drupal ajax framework, that's just because there no other way to test forms for field widgets, formatters and Views plugins.

[Chi-teck]

The only JS file generated by DCG is fairly trivial and doesn’t require extensive testing. There was a generator for CKEditor plugin that produced a bunch of relatively complex JS files. But it was removed to reduce maintenance costs.

[Chi-teck]

WebDriver tests never worked on GitHub CI because they are slow and tend to fail more often then other. Though I suppose it is possible to configure GA to run them. When WebDriver host is not reachable PhpUnit just marks the tests as skipped. I ran these tests occasionally on my localhost with local Google Chrome instance.

[Chi-teck]

Something might be changed in the latest PhpUnit versions. I would just drop these tests or exclude explicitly.

[Chi-teck]

I think it is time to deprecate this project.

AI-based code generation tools have changed the landscape significantly. They offer more flexibility and context awareness than template-based generators, which makes the ongoing maintenance effort harder to justify.

What does everyone think?

[weitzman]

That makes some sense, but then again the ongoing maintenance is also reduced by AI. Small updates and major refactors can be outsourced to the bots. I personally would love to see this project continue.

[Chi-teck]

Meanwhile, I granted @weitzman access to this project.