Hi Rene, Thanks for replying and confirming your vote a non-binding.
The speed and cadence around releases may be slow which depends on how much bandwidth contributors have; mere lack of release shouldn't be interpreted as the project or sub-project become a graveyard. The CloudStack Kubernetes provider indeed has issues and PR activities and a release being discussed - https://github.com/apache/cloudstack-kubernetes-provider/issues/16, the main blocker on it so far was where do you release it (since most people want container builds) which has been solved recently by procuring access of dockerhub project by some PMC members under the official apache org (with help from ASF infra). Until k8s v1.15, the provider was shipped with k8s upstream so an immediate release after migration of repository was not necessary. Regards. ________________________________ From: Rene Moser <m...@renemoser.net> Sent: Monday, April 19, 2021 17:56 To: us...@cloudstack.apache.org <us...@cloudstack.apache.org> Subject: Re: [VOTE] New life to Terraform Provider CloudStack with Apache CloudStack project Hi Rohit On 19.04.21 13:37, Rohit Yadav wrote: > Hi René, > > From the discussion thread on the terraform provider, you can see some > interest and commitment (https://markmail.org/message/xultlpdihdrrg4gq) and > quite recently Peter/Fraunhofer and I/ShapeBlue had a meeting with > Chris/Hashicorp to discuss and understand the handover/fork of the archived > provider repository that Hashicorp is unable to maintain it and we agreed on > the next steps; following which I started this voting thread. > > I think from a project point of view when integrations are not being > maintained by external projects, we should have a home within the Apache > CloudStack community to keep them alive and it makes it easy for ACS > contributors to work on it. There is nothing wrong with other > providers/plugins being brought in by contributors if there is interest and > demand in the community. We've done this before already, when the Kubernetes > project removed providers from their codebase we created a new home for it > within ACS project to be maintained and used by the ACS community: > https://github.com/apache/cloudstack-kubernetes-provider > > Can you reconsider your vote? Or, is that a -1 binding vote (i.e. a veto)? > Thanks. I am still -1 but non-binding, My point is "we give it a home" is not the same as "we as members of ASF care, develop and maintain it". I would't like it when the ASF becomes a graveyard of unmaintained Cloudstack integrations. Looking at https://github.com/apache/cloudstack-kubernetes-provider, it doesn't look like it gets much care either, there's not even be a release yet. Regards René rohit.ya...@shapeblue.com www.shapeblue.com 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK @shapeblue
