Since SF likes to play whack-a-mole with products that it doesn't like, let's get the decision to hate Otto out of the way early.

Otto, if you hadn't heard, is the successor to Vagrant.

I think this is a natural candidate for excluding because it deals with Tech Professionals doing their jobs, even if that means Developers deploying code and having environments consistent with production, and that would help address the "Works on my machine" problem...


1 Answer 1


First, what's with the snark?

If you hadn't noticed, the three most upvoted answers on that question (1, 2, 3) proposed that yes, we would accept questions about vagrant, provided that it is otherwise on-topic.

The same will hold true for questions about Otto.

  • 2
    Possibly. I'm still reserving judgment on it; anything that advertises that it lets developers deploy to production worries me. Commented Oct 8, 2015 at 14:50
  • 3
    Understood. There are a ton of utilities that would let developers deploy to production, and I don't think that we should throw the baby out with the bathwater. With both Otto and Vagrant, I think a more nuanced approach is warranted. I'll gladly close questions for both if they're blatantly off-topic.
    – EEAA
    Commented Oct 8, 2015 at 15:27

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .