Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think you probably have a valid point that many companies have invested a lot in customizing and tweaking their Jira installs and then built a lot of value on top of that customized and tweaked Jira installation, and convincing those companies could be a real challenge.

But we've also talked to many, many teams that use a relatively vanilla install of Jira just because it's what people are used to doing ("no one ever got fired for picking Jira"). In quite a number of cases, we've convinced these teams to switch to Kitemaker. As we mature the product, improve our developer offering and build out our ecosystem, we're confident we'll convince even more.



At my workplace:

Jira is all over, sometimes customized and tweaked, but we could be convinced to switch. Jira licensing has become a big problem.

For security reasons, we have dozens of little disconnected networks. Each one needs a separate server with a separate license, purchased separately. All software updates have to come via physical media, typically a DVD-R. That's way too many enterprise licenses to purchase.

It's like that with all types of software. If we want Ubuntu updates, we mirror the entire Ubuntu repository onto physical media and then carry that into the room. The physical media is then destroyed, even if it is a hard drive. You're not getting info out of that room.

Usually we want to deploy on a plain Ubuntu box. Sometimes we might use VMWare.

Network speeds are normally fast, but sometimes a whole-network VPN (not browser based, not on a workstation) connects sites that are 1000 miles apart. Be sure to always test your software with high network latency.




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

Search: