Hacker News new | comments | show | ask | jobs | submit login

Since they're apparently planning paid Business and Enterprise versions, I wouldn't be surprised to see at least one of those be a fully in-house solution. If they're not letting people do their own installs they may follow the path of the Google Search Appliance.

On the other hand, it may not be affordable depending on the size of your shop, but that's a different matter.

We are planning new features for those products, but we've already been selling those things for over a year: https://trello.com/business-class https://trello.com/enterprise

We also have no plans to make an in-house solution. While the tide has not 100% turned, in most places at big companies like Amazon and Microsoft, they can already use SaaS solutions (you sign a big contract, but even if your app is on AWS, msft employees can use it). For the companies that cannot, the added complexity to development and support is likely not worth it (for us).

Somewhat off-topic, but on https://trello.com/enterprise, you say that you provide "24 x 7 x 365 incidence response" where I think you mean "24 x 7 x 365 incident response".

Regardless of what word comes next, it should probably be "24 x 7 x 52".

Since a business closing does not typically occur in week-long increments, probably not. "24 x 7 x 364" is generally understood to mean one day off a year (usually Christmas Day in the US), and "24 x 7 x 51" would not be clear at all.

we're enormous, with all the fun that entails, but for a purchase to be involved, the following criteria must be met:

1) it must be sufficiently expensive. free is bad 2) i must convince everyone on my department that this is "the new way" that we operate (i.e. everyone has to use trello just like I would) 3) i must show through some pseudo science how it improves efficiency to several layers of management

Unless something is super compelling, it's not worth the effort. And if it is super compelling, it probably won't be approved anyway.

I guess I'm pretty jaded about the whole thing. If there is a neat tool, or some productivity enhancement/stress reducer, I usually just find a way to use it myself under the radar and don't share it with anyone (which offends me greatly as it's a terrible waste).

I'd actually have to go through that process for emacs 24, though in that case it's getting past the IT gatekeepers and proving to them that emacs 24 won't bring down the cluster. So I find a way to compile and run it and just don't talk about it a lot.

But anything web appish is out of the question. I settle for org-mode in emacs, but it'd be nice to collaborate. Sadly with our process of onboarding something, there's no room for experimentation or feeling something out or developing a workflow that would be worth demonstrating.

That sucks man.

I used to work at a client site where they wanted us to list all of the tools we used (as software developers) because they didn't want us to use these "computers" that we were using, in their offices on their network, and instead they wanted us to all code using citrix dumb terminals.

I no longer work at that client site, or for the company that sent me there.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact