I don’t think it’s conceivable that any reasonable number of employees could satisfy the demand of maintaining the first-party provider set in the current form, without leveraging the community. However, I for one will not sign a CLA that allows proprietary relicensing, and I’d guess most people who could give meaningful reviews are in a similar boat, or already work on the provider teams.
However, I’m also not sure that there is a “priority problem” as such - most providers don’t make HashiCorp money from consumers or contributors, and employee time is better spent on products which contribute to a positive bottom line.
The Terraform Provider Registry has made it much more palatable to run a fork of any given provider than it was previously - I’d recommend doing so if you have functionality you need that hasn’t been integrated.
Why the objection?
For it to have a material effect, both (a) Hashicorp would need to take Terradorm proprietary within a few years while your use actively need updates, and (b) there would have to be no one else maintaining a fork based on the existing MPL2[3] code.
They say[2] why they need a CLA, which doesn’t seem deceptive.
From the CLA[1] “you reserve all right, title, and interest in and to Your Contributions”, which is unlike the FSF which demands copyright assignment[4] “Put simply, this is the legal transfer of copyright on a program from the developers to the Free Software Foundation.”[5].
[1] https://www.hashicorp.com/cla
[2] https://www.hashicorp.com/blog/introducing-a-cla
[3] https://github.com/hashicorp/terraform/blob/main/LICENSE
[4] https://www.gnu.org/licenses/why-assign.en.html
[5] https://www.fsf.org/bulletin/2014/spring/copyright-assignmen...
I would also not assign copyright to the FSF.
https://registry.terraform.io/search/modules?namespace=cloud...
https://github.com/orgs/cloudposse/repositories?q=aws+terraf...
I have a lot of respect for the team personally (as in myself), though I do recognise what you say completely too. I just think there's a lot of focus on trying to do things right, and long-term-maintainably, that it often presents with a poor outlook or like there's a lack of interest.
@apparentlymart from OP in particular - I have no idea who he is in Hashicorp hierarchy, I just recognise him from GitHub - in particular is really excellent in responding to good issues and adding information along the lines of 'yes we want this but unfortunately XYZ so we're hoping PQR is going to make this easier but first we need to ABC so yes but sorry not a priority right now' sort of thing.