Who can approve Pull Requests on molecule-plugins and do releases?

Project Discussions
1

Hi all together!

Molecule was just recently released in version v26.6.0, and there were about seven other releases in the last year.

Molecule Plugins is still at the same state as last year, and v25.8.12 was released in August 2025. There are 35 open Pull Requests waiting for review and approval: half fixing things, the other half adding features.

I asked in the Matrix room #devtools:ansible.com twice and received no response, so I’m hoping someone here can help.

The project is in poor shape and falling behind the rapid development of Ansible, and even behind Molecule itself.

Greetings,
Daniel

2 Likes
2

I’d guess that @cidrblock and @ssbarnea still have the necessary rights. But :person_shrugging:

2 Likes
3

The first PR to review and merge should be: fix: docker driver compatibility with ansible-core 2.21 by wh-zfy · Pull Request #364 · ansible-community/molecule-plugins · GitHub

1 Like
4

Nothing has happened so far. @felixfontein, do you know who I can get in touch with to get an answer?

5

Maybe the @CommunityEngTeam can help.

6

Surprise! It turns out I myself can approve pull requests for “molecule-plugins.” :smiley:

And that’s exactly what I’ve just done.

7

Congrats on commit rights :slight_smile:

1 Like
8

But I still need someone else to review my PRs

9

And I did a release. But now I need to move this forward: Initial import by apatard · Pull Request #7 · ansible-collections/community.vagrant · GitHub

Any ideas who could help?

10

Hey @ziegenberg

Thank you for your work on the molecule-plugins and the community.vagrant collection so far.
I’d like to offer my assistance with helping maintain molecule-plugins and community.vagrant :slightly_smiling_face:

Molecule Plugins

Is there any specific area you’d like me to look at first?

FYI I forked molecule-plugins 3 weeks ago and have been chipping away in my fork at trying to do some tidy up which I think is related to some work you were doing too in chore: replace pre-commit with prek and align lint tooling with molecule by ziegenberg · Pull Request #384 · ansible-community/molecule-plugins · GitHub, I had planned to eventually submit these changes back to ansible-community/molecule-plugins:

Do you think this would be beneficial?

Full disclosure, I used AI to assist me with these changes:

Community Vagrant

I checked the collection and there is linter configuration for: black, mypy, pylint, flake8, ruff, and yamllint. That’s a lot of linters :smiley: - What are your thoughts about using ruff and ansible-lint. Ansible Lint runs yamllint and has its own internal ruleset we could have compatibility with. It would also reduce the number of configuration files in the repo too, and help reduce long term maintenance burden.

Also, now that the vagrant driver has been migrated to community.vagrant, I believe the original intent was to direct users to adopt that and deprecate the driver in molecule-plugins?

11

While ruff can cover black and flake8, it can only cover a subset of pylint. Because of that, removing pylint from the list sounds like a bad idea to me.

1 Like
12

Hi @dbrennand,

I’d love to see some support in maintaining molecule-plugins and community.vagrant. I’ll incorporate some of your changes into the current PR work to reorganise the tooling. I want to align it with the upstream molecule project, so both have similar DX. I’d love to get your review of the PRs so we can merge them.

Regarding community.vagrant:

Also, now that the vagrant driver has been migrated to community.vagrant, I believe the original intent was to direct users to adopt that and deprecate the driver in molecule-plugins?

That’s why there is Fix vagrant module in playbooks by 0x4D616E75 · Pull Request #314 · ansible-community/molecule-plugins · GitHub

Greetings,
Daniel

13

Good point, thanks @felixfontein. I was just reading up some more on How does Ruff’s linter compare to Pylint? :slightly_smiling_face: TIL.

OK, I was referring to the removal of the vagrant driver entirely from src/molecule_plugins/vagrant, if not, future changes to the vagrant plugin in molecule-plugins will need to be continuously backported to community.vagrant?

Now that community.vagrant is seeded with the vagrant module, should we create some documentation to assist folks with migrating to use the collection module rather than the driver.