Looking for a new maintainer with GO experience
codylane opened this issue · 0 comments
Hello,
Vagrant will be moving from Ruby to Go in Vagrant 3.x. Here's a press release about it:
I've already received emails from the Vagrant team asking for feedback about new API plugin system and ways to mitigate the new challenges of porting plugins from Ruby to Go since this plugin has been so popular. It is pretty darn cool that this plugin was named as one of the most widely used plugins and the contributors of this plugin should feel proud that this plugin has been successful over the years given all the contributions and feedback. Thank you to all who have helped make this plugin better for all. We believe in a Eco-system that just works and I feel as though this plugin has served it's purpose over the years and does exactly what it intended to do for the services it supports.
When Vagrant 3.x is released ,vagrant will be entirely written in Go with some sort of API compatibility with Ruby, but Ruby will need to be managed outside of Vagrant making it a bit complex to release and test plugins. It's entirely possible that this plugin will continue to work as a ruby based plugin. All of that is being discussed by the vagrant team and plugin writers.
I will be stepping away from this plugin over the next year and will no longer be implementing new features since Vagrant 3.x will be Go instead of Ruby.
While I've enjoyed my time helping with this plugin over the years, I think it's time that I step away and start to focus my time in areas where I can make a larger impact. I just don't have the cycles to learn GO and port this plugin to GO nor do I really want too. I think GO is a fine language, I just don't have the need or desire to learn yet another programming language and be proficient in it and it's testing model.
Thank you to all who have helped make this plugin so popular and I wish you all the best. It's been a fun journey.