Why not v2 on vmware-go-kcl?

[arl]

Describe the bug

Hi.
I've been using intensively vmware-go-kcl. I've also been contributing. I'm a bit surprised of the creation of this repo, since it's not the usual way of doing things in Go. Creating another repo makes it harder for users to follow along, spread your recognition out (GitHub stars but not only).

My questions :

• Why did you create another repo rather than a v2 in the original repo?
• What are the features that this new version repo offers?
• Will the previous repo be maintained?

Thank you

Reproduction steps

NC

Expected behavior

NC

Additional context

No response

[cmckelvey-vmware]

I can't speak 100% to the original reason, but it is my understanding that this repository is not "v2" as in a re-write, but rather the same general implementation that uses aws-go-sdk-2 (which is it's own repository as well).

Seeing as this project exists in the wild already and is potentially already being used, I don't see the project structure changing anytime soon.

Closing this ticket for now as it is not a bug.