Fun fact, I first "launched" Vagrant on HN almost exactly 1000 days ago: http://news.ycombinator.com/item?id=1175901
A bit of constructive criticism:
The "this changes everything" thing has become way, way, overplayed. I saw that and immediately rolled my eyes and stopped reading. It is about at the level of "code ninja" now.
"You can have the same environment shared by everyone, and still look like Dev/QA/Production?" they ask.
It's amazing how far behind some companies are on the tech curve.
It usually means "bridge" (橋) in the name Hashimoto, but can also mean "chopsticks" (箸) or "edge" (端), with a slightly different pitch (largely indistinguishable for non-speakers)
I suppose my only question is if you plan on redesigning the Vagrant Docs website to be more like your attractive company landing page.
As much as it's entirely irrelevant to Vagrant-as-a-tool itself, I'd love to see a whole 'brand identity' in the same theme. It's a small thing, but it makes me slightly happier when the tools I use have a little bit of character to them. (See also: Github & Octocats)
It is still not clear to me what the business model will be: will you be charging for selling extra providers (like VMWare Fusion), support contracts or ...?
For instance, once you have scripts that download and compile apache, php, python, and perhaps mysql and postgres, you can automatically create a new virtual machine with any combination of those things at any time. Even your applications can be automatically installed in a fresh development environment with a single command. It's great for allowing new developers to get going in their own environment on a team project, and good for you individually, if you have a lot of different things on the go, you can keep them isolated in their own environments and easily setup and destroy them at any time.
The value is adds is great, although it also adds a bit of inconvenience. If your OS likes to update virtualbox a lot, vagrant might suddenly stop working until they update it. Developing the scripts to provision a vm can take quite a bit of time. If you're doing lengthy compiles in the process and those compiles are failing, it can be slow to find out why. Once you get a module down, and it's solid, it's very nice to have.
I think having a Vagrant as the mascot for Vagrant is the only obvious option.
Also, why the only obvious option?
Why couldn't it be a Puppy, Cat, Horse, Printer, Cloud, Keyboard, Fish, or anything else? Why the Vagrant? Its not obvious. For all the client know Vagrant might be an acronym or some made up tech name.
I have a few questions:
When did you think about the first time and when did you really decide to do this step?
How do you start? Bootstrap it by your own or try to go with for a VC?
How are you planning the addon open source/paid addon ratio will be like?
I wish you all the best for your company.
And because I've been using Vagrant every day: Thank you very much.
The inkling of a possibility of something like this only entered my head around March/April 2012. I committed to the idea in June 2012.
> How do you start? Bootstrap it by your own or try to go with for a VC?
I'm attempting to bootstrap it on my own for now, because I think I have a solid foundation so there is a clear line to revenue. Of course, my runway to do this is much shorter than if I had VC funding. On the other hand, I have a lot more freedom without VC funding.
> How are you planning the addon open source/paid addon ratio will be like?
There will be many more open source add-ons, and I think it should be this way.
Thank YOU for using Vagrant. :)
Vince the Vagrant is being retired.
Also, the website looks absolutely gorgeous. Fantastic work there.
Virtualbox has been the main provider it manages. Part of this announcement includes adding support for more providers!
Surely you can't trademark a cube?