3 ms·
A few years ago, there used to be community reviewers of pull requests to the AWS provider - indeed I reviewed dozens after leaving HashiCorp. My own access for
by jen20 5y ago
A few years ago, there used to be community reviewers of pull requests to the AWS provider - indeed I reviewed dozens after leaving HashiCorp. My own access for this got removed in (IIRC) late 2018, and I’d assume this was across the board.
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.
- robocat 5y ago> I for one will not sign a CLA that allows proprietary relicensing 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 https://www.hashicorp.com/cla [2] https://www.hashicorp.com/blog/introducing-a-cla https://www.hashicorp.com/blog/introducing-a-cla [3] https://github.com/hashicorp/terraform/blob/main/LICENSE https://github.com/hashicorp/terraform/blob/main/LICENSE [4] https://www.gnu.org/licenses/why-assign.en.html https://www.gnu.org/licenses/why-assign.en.html [5] https://www.fsf.org/bulletin/2014/spring/copyright-assignment-at-the-fsf https://www.fsf.org/bulletin/2014/spring/copyright-assignmen...
- jen20 5y agoBecause the MPLv2 license grants all the rights I'm willing to part with. I don't see it as deceptive, just as unnecessary. I would also not assign copyright to the FSF.