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

Atlassian acquires Trello for $425M

techcrunch.com

Post reply on HN
Print view View original

411–420 of 765 posts

Re: Atlassian acquires Trello for $425M

#411

Post by brianwawok »

misiti3780 wrote: post #395
BinaryIdiot wrote: post #390

Earlier quoted context omitted.

To be fair I've been a part of 3 acquisitions and have seen this story play out tens of times with beloved software. It always starts out this way. "The original folks are going to run it, not the new company!" "Things will stay the same" yadda yadda yadda. 1-3 years down the road, it'll be a different story. It'll be unlikely that the executive team will stick around past whatever agreement they signed with Atlassia…

it has worked out for instagram so far - no ?

How many handcuffs have expired?

Re: Atlassian acquires Trello for $425M

#412

Post by farkas »

ryanSrich wrote: post #98
rb808 wrote: post #82

Earlier quoted context omitted.

It makes sense mainly because Trello is a competitor to Atlassian and its best to kill it now before it takes too much market share. edit: Yes right now there might not be an exact competitor but in a few years it could easily match everything Jira does.

Is Trello really a competitor though? JIRA and Trello couldn't be more different. I'd think Trello and Asana are much closer competitors. JIRA is like an over engineered spaceship with more features than anyone could learn in a lifetime. Comparatively Trello functions more like a Prius. Priuses and spaceships don't compete.

We don't view JIRA and Trello as competitors.

JIRA shines in areas that (a) have workflow and (b) require repeatable processes across a number of people.

Once you have 20+ people on a project, you need repeatable processes.

In cases like bug tracking, project management, customer service, help desks, HR onboarding and hundreds others you need workflow.

Trello shines in areas where you have (a) small teams or (b) require ad-hoc semi-structured data.

In small teams, even if repeatable process would help you, it's not worth the cost of setting up a system - you achieve it by social means.

Trello also has many, many use-cases where you want to start something quick, or personal. In this case it really shines, with near-zero friction to get started.

Scott, CEO Atlassian

Re: Atlassian acquires Trello for $425M

#413

Post by iamaelephant »

creativityhurts wrote: post #333
vecter wrote: post #330

Earlier quoted context omitted.

Can you put in concrete terms why you see this as a problem?

Atlassian will most likely "sunset" Trello or somehow include it in JIRA.

I don't have any information one way or another but to my knowledge Atlassian has never done this with an acquisition.

Re: Atlassian acquires Trello for $425M

#414

Post by jlarocco »

BinaryIdiot wrote: post #390
mhp wrote: post #366

Earlier quoted context omitted.

The Trellists made Trello. And the Trellists are going to keep working on Trello at Atlassian. Atlassian understands that Trello is unique and beloved and they definitely do not want to mess that up. Read this article that Jordan Novet wrote. I know seeing is believing and you will have to wait and see, but I agree with everything Jay Simons says in this interview. "During the interview, Simons took time to assure me…

To be fair I've been a part of 3 acquisitions and have seen this story play out tens of times with beloved software. It always starts out this way. "The original folks are going to run it, not the new company!" "Things will stay the same" yadda yadda yadda. 1-3 years down the road, it'll be a different story. It'll be unlikely that the executive team will stick around past whatever agreement they signed with Atlassia…

Exactly. No acquisition ever starts off with, "We're going to change a bunch of stuff as we assimilate this new company."

It's not hard to find "______ is being acquired by ________" headlines on HN, where everybody involved promises not to change anything, and then find the corresponding shutdown post on https://ourincrediblejourney.tumblr.com/ sometime a few months later.

Unfortunately, even if Jira were really serious about not changing anything, it's not entirely up to them. No doubt there are some Trello employees who don't want to work for Jira, and a lot of them will eventually leave.

Even if everybody at Trello honestly believes it, in a few months it's not going to be their decision any more.

Re: Atlassian acquires Trello for $425M

#415

Post by problems »

jessaustin wrote: post #391
problems wrote: post #371

Earlier quoted context omitted.

The attitude is simple - don't give your code, and especially don't give access to your devops repositories to 3rd party companies who simply don't need it. If a security vulnerability happens on the public Fogzbugs instance, we'd be bitten by it badly in this sort of situation. In our setup, we protect against that by exposing the JIRA webserver and git servers only inside of our private network. It's not about perf…

Thanks for the detailed reply. The downtime issue is certainly understandable. I hope you're keeping customer data out of DVCS, but it's true that flaws in your code might be more "discoverable" if an attacker had that code. It does introduce another step into the attack, however, to have to hack FogBugz before reading your code and discovering the flaw that hacks your services. You know your threat model better than…

I'm not too concerned about someone getting the code, reading it and discovering a flaw allowing for exploit. I'm much more concerned about someone being able to modify code that will be pulled onto production systems by build and deployment scripts (not to mention the build and deployment scripts themselves) which would allow direct access without any need to hack anything beyond the external cloud service. Even a disgruntled admin at Fog Creek in this case could do something like this without the need to hack anything.

Re: Atlassian acquires Trello for $425M

#416

Post by farkas »

mhp wrote: post #293
SonOfLilit wrote: post #254

Open letter to Atlassian: Trello are an amazing team and an amazing product, and what makes the product so amazing is how domain-agnostic it is. They refuse at all costs to add any feature that helps use Trello in one specific way over others (e.g. lists = stages in task lifetime, cards = tasks; lists = assigned people, cards = tasks; lists = dates, cards = events, ...), and that made Trello equally useful as a Kanba…

Thank you for the kind words. I promise you Atlassian understands why Trello is so successful. You described Trello's core strength perfectly - and this one of the reasons they are committed to keeping it as a standalone service. (disclaimer: I'm the CEO of Trello)

I want to add to what Michael said above.

In meeting with Michael, and discussing how we could work together, Michael could not be more clear that Trello's success is predicated on is breadth and its appeal to many different use-cases.

This is most clearly displayed in their inspiration page, that includes many, many use-cases:

  https://trello.com/inspiration
Keeping this strength alive will be key to Trello's long-term success.

Scott, CEO Atlassian

Re: Atlassian acquires Trello for $425M

#417

Post by r_smart »

BinaryIdiot wrote: post #393
jupp0r wrote: post #386

Earlier quoted context omitted.

Just out of geniune curiosity: what's not bad?

JIRA can do anything. LITERALLY. The configuration of a new JIRA server, projects, etc is insane. It just doesn't do anything explicitly well IMO. It's also crazy slow and their enterprise hosted version still has maintenance outages which, as a software developer in 2017, I find absolutely appalling.

|their enterprise hosted version still has maintenance outages

Even WoW doesn't really do that anymore :)

Re: Atlassian acquires Trello for $425M

#418

Post by dlp211 »

anildash wrote: post #160
yeasayer wrote: post #33

Why did Fog Creek approved this acquisition? With products like Stack Overflow, Trello and GoMix I thought they want to become a big player on the market of software development. Why sell our own assets?

Fog Creek and Trello are two separate companies that share cofounders (and an office here in NYC!) so we at Fog Creek are happy for Trello but it's not an asset of ours.

But a bunch of Fog Creek employees had ownership/shares in Trello no?

Re: Atlassian acquires Trello for $425M

#419

Post by hackergirl88 »

Here is a snapshot of what Bitbucket has launched over the last year: Server/Data Center: http://blogs.atlassian.com/2016/12/bitbucket-server-year-rev...

Cloud: https://blog.bitbucket.org/2016/09/07/bitbucket-cloud-5-mill...

- Merge checks - Bitbucket Pipelines (Continuous delivery service in Bitbucket Cloud) - 2FA - Universal Second Factor (U2F) - Improved SSH - Support for multiple SSH keys - Build status API - Smart Mirroring - Git LFS (including the embedded media viewer only in Bitbucket Cloud which allows for better large file uploads) - Smart Commits (allow repository committers to process JIRA issues using commands in your commit messages) - reviewer status on pull requests - Code search (Server only currently) - 0 downtime backups - code review at commit level - default review in pull requests - pull request merge strategies - Deploy Bitbucket Data center with AWS - iterative reviews for pull requests - pull request focused dashboard - Bitbucket Connect add-ons (deploy from Bitbucket with AWS, Azure or Digital Ocean)

Re: Atlassian acquires Trello for $425M

#420

Post by iambateman »

iamaelephant wrote: post #409
pc86 wrote: post #372

Earlier quoted context omitted.

I'm sure you made quite a large sum of money off of this deal, but Atlassian doesn't have a great track record of purchasing non-Atlassian products and not messing them up. And... "Trellists?" They're just people.

Which products do you think Atlassian messed up after acquisition? Disclaimer I'm an Atlassian employee, but just curious.

I'm not sure about acquisitions, but compared to github, jira and bitbucket are poor.

I tried to figure out what confluence even does and I'm still not sure.

Considering I'm forced into the atlassian ecosystem at work, this is my plea for y'all to improve.

Post reply on HN