[RESULT] [IP CLEARANCE] CloudStack Terraform Provider project contribution

There were no -1 votes, therefore this IP clearance vote passes by lazy consensus. Thank you! Kind regards Paul Angus From: pau...@apache.org mailto:pau...@apache.org> > Sent: Tuesday, July 20, 2021 9:51 AM To: general@incubator.apache.org

[RESULT] [IP CLEARANCE] CloudStack Go SDK project contribution

There were no -1 votes, therefore this IP clearance vote passes by lazy consensus. Thank you! Kind regards Paul Angus From: pau...@apache.org mailto:pau...@apache.org> > Sent: Tuesday, July 20, 2021 9:51 AM To: general@incubator.apache.org

RE: [IP CLEARANCE] CloudStack Terraform Provider project contribution

There were no -1 votes, therefore this IP clearance vote passes by lazy consensus. Thank you! Kind regards Paul Angus From: pau...@apache.org Sent: Tuesday, July 20, 2021 9:51 AM To: general@incubator.apache.org Cc: Rohit Yadav Subject: [IP CLEARANCE] CloudStack Terraform Prov

RE: [IP CLEARANCE] CloudStack Go SDK project contribution

There were no -1 votes, therefore this IP clearance vote passes by lazy consensus. Thank you! Kind regards Paul Angus From: pau...@apache.org Sent: Tuesday, July 20, 2021 9:51 AM To: general@incubator.apache.org Cc: Rohit Yadav Subject: [IP CLEARANCE] CloudStack Go SDK project co

[IP CLEARANCE] CloudStack Go SDK project contribution

Hi Incubator PMC, The Apache CloudStack PMC has voted to accept the donation of " CloudStack Go SDK", which is a web based API for CloudStack [1]. Please vote to accept this contribution. This is a lazy consensus majority vote, per the IP clearance process [2], open for at least 72 ho

[IP CLEARANCE] CloudStack Terraform Provider project contribution

Hi Incubator PMC, The Apache CloudStack PMC has voted to accept the donation of " CloudStack Terraform Provider", which is a Terraform provider for CloudStack [1]. Please vote to accept this contribution. This is a lazy consensus majority vote, per the IP clearance process [2], open f

Re: IP clearance officer for accepting Terraform

Thanks Justin, We believe that we have now. They are mostly from the same person/company, but as they're going to go into two distinct repos, and do different things - one is a library which can facilitate a whole load of things including the other the feature in the other repo. I'm leaning to

FW: IP clearance officer for accepting Terraform

Hi, me again, To recap; We (the CloudStack Project) are bringing in some Terraform plugin code to pick up its ongoing development and maintenance. It's split into two discrete repos in its external form, and will be keep in two discrete repos under the Apache repos. There are different commi

FW: IP clearance officer for accepting Terraform

Sorry, me again. As these two codebases are being brought over into two separate repos, and referred to as distinct entities, do they need separate Codebase IP Clearance XML files and then separate entries in index.xml ? Kind regards Paul Angus From: Rohit Yadav Sent: Wednesday,