431–440 of 765 posts
Earlier quoted context omitted.
Hmm, they show up for me [1]. That screenshot is an HTML file but I also looked at JS, Python and Markdown and all were showing syntax highlight in diff commits. 1. https://i.imgur.com/Av70r03.png
this isn't syntax highlighting, it's highlighting the diff add/removes. https://github.com/torvalds/linux/commit/b0b9b3df27d100a975b... syntax highlighting would be like this, where keywords, function calls, and variables are all different colors.
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…
I also feel like (and I realize many disagree) that YouTube largely kept its "feel" and didn't turn into Google Videos 2.0.
Of course there are plenty of examples of exactly what you describe. I feel the same way about Java, Hudson (lol) and plenty of other acquisitions.
Earlier quoted context omitted.
Googling around, the definition that comes up is: > Damning with faint praise is an English idiom for words that effectively condemn by seeming to offer praise which is too moderate or marginal to be considered praise at all. Which seems about right to me. It's like writing an employee a letter of reference, and only saying that they're very punctual - meaning that there's nothing else good about them, other than the…
"Damning with faint praise" is a pretty subtle English idiom. In my experience, it's only used to refer to an instance where someone is socially obligated to offer praise, e.g. a doctoral adviser writing a reference for their student, who gives such faint praise that they intend the recipient to infer that, were they allowed to, they would have been explicitly critical. Since the comment author in question was under…
Earlier quoted context omitted.
Atlassian will most likely "sunset" Trello or somehow include it in JIRA.
They don't really have a history of doing that. Greenhopper was acquired and integrated into JIRA as JIRA Agile. Hipchat was acquired and now it lives on and nicely integrates with nearly all Atlassian products (JIRA, Bamboo, Confluence, etc). My guess is they'll keep Trello running for a while as-is, and slowly rework it to become "JIRA Lite". It will likely have Trello-like functionality with JIRA branding, and som…
Slack has more speed, better integrations, better search, reliability. (For example, getting notifications on iOS.
I hate HipChat. Apologies to those that love it, but it's likely you never used both side-by-side during normal working days to compare.
So if Atlassian tried to put their mark on Trello, I have little confidence that it will still be Trello.
Earlier quoted context omitted.
Congrats! However, I'm still pouring out a little wine on the ground for my fallen homies who died a slow death from being Jira'd and Bitbucketed and Confluenced to the point that their will to live was crushed. Being the anti-Jira is what made Trello great. If feels like Luke Skywalker just got bought by the Dark Side while claiming that nothing will change -- I'm still with the rebels.
I feel like I'm the only one that likes Jira more than Trello. I started on Trello, then moved to a company that uses Jira, and couldn't be happier. It's just so functional . Why does everyone hate on it?
Your experience will depend on the plugins you've installed, how you've configured custom fields and workflows, your org's SSO policies, the hardware you're deploying it to and how well you keep it up to date (if you're deploying on-prem), etc.
Earlier quoted context omitted.
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.
At that same company, we switched to Jira from 6 or 7 different ticketing systems (a mix of in-house and third party systems split up by department). It was a herculean effort to transition, but the result was much better than any of the individual ticketing systems with the huge benefit of just opening a ticket anywhere and moving it to where it needs to go while preserving the history.
Now the cons I've seen are; I have no idea how much it costs and it seems to require a small to large team to manage and deploy it for maximum usefulness. For ad hoc deploys I've heard/seen performance issues if the server isn't beefy or configured correctly and the UI can be inscrutable if users are just dropped into the default. That's about (the best case scenario of) what I expect for enterprise software, though.
I have used GitHub Enterprise and haven't used BitBucket. I might not be using it correctly, but I don't see what's so great about GitHub Enterprise (especially for the cost). We still have to use a separate ticketing system for non-project related things (same with documentation).
I've used different ticketing systems since leaving the place that used Jira/Confluence, but have been disappointed at what they were using and what else I could find out there. What have you found out there that has worked better?
Earlier quoted context omitted.
What do you like instead of Jira? I dont like Jira either but I do like bitbucket. I started using it back in the day because besides public hosting they also gave me free unlimited private repos and found it does everything I need.
I hate bitbucket. $12 or so per month for private repos is an extremely small price to pay for an infinitely better UX, better integrations and just all all around better experience. For a tool I use multiple times per hour, "free" doesn't matter much to me. Github isn't perfect, but it's damned close. As far as Jira -- the tool itself isn't bad per se, but the way PMs turn it into their own little power-trip kingdom…
Earlier quoted context omitted.
Hmm, they show up for me [1]. That screenshot is an HTML file but I also looked at JS, Python and Markdown and all were showing syntax highlight in diff commits. 1. https://i.imgur.com/Av70r03.png
this isn't syntax highlighting, it's highlighting the diff add/removes. https://github.com/torvalds/linux/commit/b0b9b3df27d100a975b... syntax highlighting would be like this, where keywords, function calls, and variables are all different colors.
Earlier quoted context omitted.
JIRA interface blows. However you're looking at it from a very selfish standpoint. The Trello team has probably been working on this for years with the explicit goal of an exit, better to get bought by likeminded product people and make a big return than to be bought by Google and have the product killed entirely.
He's a customer.
This is depressing. Trello is a beloved software for a lot of people. It's sad that Trello decided to sell off to Atlassian. I can't believe the same company that makes Jira is going to run Trello. SourceTree is the only software that they make that doesn't suck.
We also used and liked Crucible (their code review tool), but it didn't yet offer some features of Gerrit that were very important to us, so we moved to Gerrit.