The effort to move the proxmox modules/plugins to community.proxmox was discussed last year at CfgMgmtCamp, but the folks involved found out that it was more work than they expected / had time for, and thus the project basically died before it really took off. Since then nobody stepped forward to take this up again - until now you did, I guess 
Right now there are a few folks who sometimes work on the proxmox modules/plugins in community.general, as you can see from the output of git log plugins/modules/proxmox* plugins/inventory/proxmox.py plugins/connection/proxmox_pct_remote.py. So there is definitely a user base around and some hands to help, at least with smaller tasks, maybe also with larger ones (I don’t want to promise other people’s free time 
).
Generally the idea is as follows:
- Migrate all modules, plugins, and accompanying tests from community.general to community.proxmox, with their commit history. (This should probably wait for improve ansible_host in proxmox inventory plugin by aapjeisbaas · Pull Request #9952 · ansible-collections/community.general · GitHub; create new proxmox_backup_schedule module by raoufnezhad · Pull Request #9592 · ansible-collections/community.general · GitHub and Proxmox `local` connection support. by reitermarkus · Pull Request #4027 · ansible-collections/community.general · GitHub can probably best be re-created in that repo.)
- The aim should be to get the collection in a workable state with basic CI, and to get a first release out, and soon a slightly polished one as 1.0.0.
- Then we can deprecate the content in community.general and add community.proxmox to the Ansible community package, and eventually remove the proxmox content from community.general 11.0.0 (to be released in June 2025), resp. replace it with redirects to community.proxmox.
- Basically from that point on the main development will happen in community.proxmox. Bugfixes added there should be re-created for community.general (since the stable-10 and stable-9 branches should still get bugfixes for some time), while PRs in community.general that are not re-creations from community.proxmox will be closed right away.
I think the main expectations are:
- Implement the move, and ping interested folks (like everyone who created a proxmox related PR in community.general recently, or also folks who created issues and look interested in helping, and of course the @proxmox-collection in the forum - which you should join, if you haven’t). I’d start with forking the community.proxmox repo and figuring out how to get the history there, and once it works the Ansible community team can help taking over the community.proxmox repo and implement it there as well. (These things usually take several tries to get right, so it’s best to not do it in the real repo right away.)
- Help getting CI up and running, at least a basic one. Running integration tests would be especially awesome (community.general only runs unit and sanity tests right now for proxmox content), but that is probably quite some work. (That’s why I would probably not require this for a 1.0.0 release.)
- Make sure that the 1.x.y releases are (mostly) backwards compatible (with explicitly documented differences, if something isn’t backwards compatible!) to the current content in community.general, to ease migration.
- At least stay around for some while to help with getting fixes and improvements merged and new versions released.
I’m sure that there are enough folks around who can help with everything, but who might not have enough time to fully work and implement one (or more) of these points.
To avoid double work, and to get the migration from c.general to c.proxmox done as fast as possible, it would be great to do this (i.e. release community.proxmox 1.0.0) before Ansible 12’s feature freeze (2025-06-17, Ansible project 12.0 — Ansible Community Documentation) and the community.general 12.0.0 release (~2025-06-15, Releasing, Versioning and Deprecation · Issue #582 · ansible-collections/community.general · GitHub).
@proxmox-collection it would be great if you could also write here if you’re interested in and have time for helping with this