Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atlassian Acquires StatusPage

techcrunch.com

Post reply on HN
Print view View original

101–110 of 132 posts

Re: Atlassian Acquires StatusPage

#101

Post by brianwawok »

cyberferret wrote: post #68
jkarneges wrote: post #62

Earlier quoted context omitted.

Status pages are best hosted offsite, which means status page companies can easily justify higher prices since the alternative is to run your own servers exclusively for the status page (can't just throw the status page software on your app server). I'm skeptical that running Cachet on your own servers would be cheaper than StatusPage's smallest plan, especially if you have any kind of redundancy in place.

Our main stack is on Amazon AWS (West Coast) and we run Cachet on a $5/mo Digital Ocean Droplet on the East Coast for redundancy. Took about 30 minutes to set up Cachet on the DO VPS. That is enough redundancy for our little bootstrapped web app until we are large enough to be able to afford something better.

And for another $5 you could likely round robin dns a vpn in Europe. Being cheap is fun.

Re: Atlassian Acquires StatusPage

#102

Post by nilkn »

ymerej wrote: post #93
gregmac wrote: post #81

Earlier quoted context omitted.

I'll also add it's not always obviously wrong when it's setup. For example, of course only QA people can use "Testing passed" transition. Of course there should be x, y, z fields filled out to be able to create the ticket. Well we're at it, let's make sure only the product manager can close a ticket with 'wontfix', and only the release manager can change a fixversion. This is a really common problem with any workflow…

For you, there is Github issues. Have fun, cowboy.

More seriously, there's FogBugz, which intentionally is not very customizable to avoid the issues the above poster was referring to.

In my experience, FogBugz is a little too limited, so I do prefer Jira, but only when used by competent people who understand that the customization should not get in the way of getting things done and it should not be used to institutionalize a lack of trust in employees.

Re: Atlassian Acquires StatusPage

#103

Post by voltagex_ »

ymerej wrote: post #93
gregmac wrote: post #81

Earlier quoted context omitted.

I'll also add it's not always obviously wrong when it's setup. For example, of course only QA people can use "Testing passed" transition. Of course there should be x, y, z fields filled out to be able to create the ticket. Well we're at it, let's make sure only the product manager can close a ticket with 'wontfix', and only the release manager can change a fixversion. This is a really common problem with any workflow…

For you, there is Github issues. Have fun, cowboy.

Having used HP Quality Centre, JIRA and Team Foundation, I think your snark is unwarranted and there is a middle ground to be found between very basic issue tracking and something completely overbearing like QC.

Re: Atlassian Acquires StatusPage

#104

Post by julianz »

dberg wrote: post #23
balls187 wrote: post #13

Earlier quoted context omitted.

Ouch. I know snark is generally frowned upon, but HipChat and hosted JIRA/Confluence downtimes have been serious issues for us.

Sorry, as a paying customer this is true. Hipchat in particular is down almost daily and its basically a running joke at this point.

Interesting. We run our entire company on (paid) Hipchat across a wide range of timezones and have very few problems.

Re: Atlassian Acquires StatusPage

#105

Post by ccrush »

yeukhon wrote: post #98
timv wrote: post #86

Earlier quoted context omitted.

Bitbucket has remained a standalone product, but I don't think many of its original mercurial userbase feel like it's been "safe". When Atlassian bought bitbucket it was the place to host mercurial repositories. Now it's a git hosting service that hasn't gotten around to turning off mercurial support yet.

It would be a terrible move to disable mercurial support since Bitbucket is pretty much the only place you can host your Hg repo remotely with reputation. Other competitors just aren't up to bar.

What do you think "up to bar" means? Where did you pick up that expression? Did you ever consider that those who use the expression "up to par," which means being ahead of the expected number of strokes on a golf course, might think that you are a moron for not knowing the correct term? I dont know if "up to bar" is an actual term people use, but I do know that some of the people aware of the term "up to par" would look down on you. I definitely am.

Re: Atlassian Acquires StatusPage

#107

Post by vadym909 »

ccrush wrote: post #105
yeukhon wrote: post #98

Earlier quoted context omitted.

It would be a terrible move to disable mercurial support since Bitbucket is pretty much the only place you can host your Hg repo remotely with reputation. Other competitors just aren't up to bar.

What do you think "up to bar" means? Where did you pick up that expression? Did you ever consider that those who use the expression "up to par," which means being ahead of the expected number of strokes on a golf course, might think that you are a moron for not knowing the correct term? I dont know if "up to bar" is an actual term people use, but I do know that some of the people aware of the term "up to par" would l…

Could it be that golf uses the term because par means equal. Its a pretty common phrase and means the same as 'not at par', 'up to snuff','not at the same level'. I've especially seen it used in hiring (high bar, below the bar, not at the bar'. Probably comes from the high jumper's bar.

Re: Atlassian Acquires StatusPage

#108

Post by mathattack »

tajen wrote: post #50
djsumdog wrote: post #11

I remember when I was doing a talk in Melbourne, another developer told me what he didn't like about Atlassian was that they essentially only had one product (was it Jira? or Confluence? can't remember) and almost everything else in their offering set; they bought from other people and re-engineered to fit into their product line. Having administered, Jira, Confluence and Bamboo servers (all with slightly different i…

Their biggest product is JIRA followed by Confluence. Let's look at acquisitions vs internal developments: - 2003: JIRA - In-house - ~2004: Confluence - In-house - ~2007: Fisheye, Crucible (code analysis) - Acquisition - ~2008: Bamboo (builds) - Acquisition - 2010: Bitbucket - Acquisition - 2011: SourceTree - Acquisition - ~2012: Bonfire (JIRA Capture - screencast bugcatcher) - In-house - ~2013: HipChat - Acquisition…

I think it can make sense. When you are a startup, you can make a bet-the-company bet. In fact, that's what your investors want. When you're a mature company, it's much harder to take the risk. (And the risk could be as simple as pulling your 3 best developers off the core product) Buying both the product and the team that built it can make sense, especially if you already have the right customer base. If you do it often enough to get good at it, you know the price to pay, and how to integrate it afterwards.

For what it's worth, serial acquirers generally get good at it and outperform one-off acquirers. [0]

[0] https://ttu-ir.tdl.org/ttu-ir/handle/2346/58897

Re: Atlassian Acquires StatusPage

#109

Post by amazingman »

ccrush wrote: post #105
yeukhon wrote: post #98

Earlier quoted context omitted.

It would be a terrible move to disable mercurial support since Bitbucket is pretty much the only place you can host your Hg repo remotely with reputation. Other competitors just aren't up to bar.

What do you think "up to bar" means? Where did you pick up that expression? Did you ever consider that those who use the expression "up to par," which means being ahead of the expected number of strokes on a golf course, might think that you are a moron for not knowing the correct term? I dont know if "up to bar" is an actual term people use, but I do know that some of the people aware of the term "up to par" would l…

What was your intent when choosing to write this comment and then choosing to publish it?

Re: Atlassian Acquires StatusPage

#110

Post by josscrowcroft »

Congratulations. I enjoyed the clear, transparent blog post, although my fundamental question "Will they shut down the service in the mid-to-long term or force us to become an Atlassian customer?" took some time to get an answer to.

I also felt their blog post was all about their journey, which while interesting doesn't really present any value for us as a customer. It would have been nice to know why the acquisition is in the customers' best interest rather than only the founders' (of course both are important).

Post reply on HN