Earlier quoted context omitted.
Could you share what markdown/git tooling you've identified?
Not speaking for the GP. I use MkDocs and keep my personal notes. The only weak spot for me is that I haven't fully grokked search and as my notes grow, it can be harder to find things. I alternate between figuring out how search and how to bolt on some other search utility. MkDocs includes a utility to publish to Github pages but I keep my notes on a self hosted Gitea server and serve using "python -m http".
Atlassian prepares to abandon on-prem server products
181–190 of 205 posts
Re: Atlassian prepares to abandon on-prem server products
#182Earlier quoted context omitted.
Do you know how this compares with the Atlassian Server (on-prem) option, let's say in the best case of 500 users?
They no longer sell Atlassian “Server edition” licenses. Just Data Center and Cloud now.
Re: Atlassian prepares to abandon on-prem server products
#183Earlier quoted context omitted.
It is pricey - I will not disagree with you. It is 1-500 is the license tier and that costs $42,000 per year for the Jira data center subscription, $27,000 for Confluence, BitBucket is $2,300 for 1-25, Crowd is $5800 for 1-500, and Bamboo is $11k for up to 25 users. I would not connect any of these services directly to the Internet.
Do you know how this compares with the Atlassian Server (on-prem) option, let's say in the best case of 500 users?
Re: Atlassian prepares to abandon on-prem server products
#184Reading this news makes me happy because I know someone somewhere is likely going to be have the chance to argue that it's time to migrate away from JIRA and Confluence. I personally they haveheld back nearly every organization I've worked for in some way or another over the last 15 years. These Atlassian products are the destroyers of enjoyment, satisfaction, project management and productivity. Issues I've encounte…
JIRA is like Salesforce or any large enterprise “customizable” software package - by default all it does is expose all the organizational chaos and insanity.
Re: Atlassian prepares to abandon on-prem server products
#185Atlassian Data Center edition will continue to be supported. It is the same software as the Server offering but with a different product key unlocking some more features like multiple nodes. It is far more expensive than Server, but still cheaper than Atlassian Cloud. And I found the per-user pricing to be about on par with alternative products from other suppliers. But for small companies, the brittleness of the lic…
And also locking out others like local Bamboo agents.
Re: Atlassian prepares to abandon on-prem server products
#186Earlier quoted context omitted.
Microsoft's "on the record" voice is always "Azure DevOps is alive and has an active roadmap". You can read that roadmap for yourself. It is kept in a GitHub repository . Last time I checked this year the last commit was sometime in 2020. The last group of features that loudly launched for Azure DevOps were branded "GitHub Advanced Security for Azure DevOps". (This is where I get the 2-3 years behind GitHub metric.)…
I used to work at Microsoft, though I left a few years before MS purchased GitHub. Post-2010s, Microsoft was still migrating many products away from Perforce/SourceDepot and into TFS, and then TFS+git around ~2015. Microsoft hacked TFS to be a git server so they could continue to use TFS for work-item/project-tracking (and no-one wanted to go back to Product Studio). That’s TFS’ strength, as far as Microsoft is conce…
I'm mostly aware of it from GitHub Universe and Microsoft BUILD demonstration videos. Both of which give me a lot of signals that Microsoft internally has moved a lot faster to GitHub than it did from predecessors to TFS/TFS+git. Some of the teams talking about it are huge ones (both in terms of size but also in terms of weight internal/external to the company).
From their own hype videos in the virtual sides of the two conferences, I certainly get the impression they reached "good enough" feature "parity" with AzDO Work Items internally a year or two ago, at least. That doesn't seem like the reason they keep saying AzDO is still alive.
I do realize that AzDO has some big enough Enterprise customers though that not spooking them can be a big reason for the weird messaging despite their overt actions and all the subtle hints that AzDO is dead. But also, my understanding is that many of those customers don't entirely care if a migration needs to happen so long as they are given a migration with a far enough out deadline. [1] I know some companies seem to be acting more spooked that there isn't a deadline yet for AzDO's shutdown. (It was a factor in my last employer migrating to Atlassian's terrible products for everything but repository hosting after years in AzDO [after years in Bitbucket and Atlassian's terrible products and hating them; vicious cycle].)
I obviously don't know what Microsoft is truly waiting for at this point to kill AzDO, which gets back to that feeling that it is something fundamentally weirder such as a superstition.
[1] Case in point: no one seems to be shouting too much about the crazy Azure AD to Entra shenanigans because it has dates and timelines! The timelines don't even make sense: among other things, Azure AD B2B and Azure AD B2C both get marketed as "deprecated" months before their Entra counterparts are expected to leave "Beta" or "Preview" statuses and even more months before automated migration tools are expected to be available. But it is all a planned migration and that makes all the difference.
Re: Atlassian prepares to abandon on-prem server products
#187Earlier quoted context omitted.
They no longer sell Atlassian “Server edition” licenses. Just Data Center and Cloud now.
Yes, I know and that's why I'm asking. I suspect many companies I know are on the "Server edition" and I'm curious how much more expensive it will get for them.
We went from Server -> Cloud -> GTFO. Server also had tiered pricing starting at $10 for 3 users. It went up from there in much saner increments but I don’t recall them.
We exited the ecosystem at the last cloud price hike. Their product pricing people are delusional.
Re: Atlassian prepares to abandon on-prem server products
#188Using Atlassian cloud products is a business risk. They previously let customers sit for weeks without access to their data [1]. Cloud-hosted products do get early patches for unsecured /setup routes though [2], so there's that. At this point the decision has been made in our org to firewall their products off the internet and internal networks, and migrate to something else by 2024. [1] https://hn.algolia.com/?q=atl…
As a former Atlassian administrator, I believe the opposite. Maintaining the system on-premise was a bigger risk. The products are too complicated to be packaged nearly with a bow for sysadmins. You inevitably start having to become at Atlassian SME just to keep that shit running. I’m all for your company going with an alternative product, but for a company who would rather stick with Atlassian products, you’d be ins…
Re: Atlassian prepares to abandon on-prem server products
#189Earlier quoted context omitted.
Could you share what markdown/git tooling you've identified?
Sure. We're focusing first on converting everything to plain Markdown and using a Git repo to manage the content. Writers can use whatever Markdown tool they prefer for this. (I'm using Obsidian and others are iA Writer.) I have yet to decide on the docs publishing tool, but I'm testing Astro, Vitepress, and Markdoc for publishing. I'm leaning towards Astro since it's very flexible, easy to add small bits of interact…
Re: Atlassian prepares to abandon on-prem server products
#190Earlier quoted context omitted.
Not speaking for the GP. I use MkDocs and keep my personal notes. The only weak spot for me is that I haven't fully grokked search and as my notes grow, it can be harder to find things. I alternate between figuring out how search and how to bolt on some other search utility. MkDocs includes a utility to publish to Github pages but I keep my notes on a self hosted Gitea server and serve using "python -m http".
Author of Material for MkDocs here. We're currently working on re-architecting the entire search engine and rewriting it from scratch. We're currently based on lunr.js, which is unmaintained as of 2020 and has more or less run its course. We've learned a lot what matters in respect to efficient and user friendly documentation search, and can't wait to give the first version into the hands of our users. I'm convinced…