Yes, there still is no easy way to migrate Tempo data from Server to Cloud. Their advice is "there's an API - good luck" [1].
Gitlab is great for their developer niche, but the relatively weak issue tracker and wiki lets them down for more general use. Still, Gitlab is a great company with momentum and a roadmap. Feel free to join us [2] in looking at such alternatives.
I would like to like YouTrack, but I've always been put off by own custom database [1]. I like my data in relational databases. SQL is the ultimate read-write API. Jira (unintentionally) stands on the shoulders of giants in this regard.
I mean under an Open Source license, which the Atlassian Software License Agreement [1] is very far from being. It forbids you to even redistribute patches between licensees.
Atlassian's Cloud products were initially (~2009) just the Server products with a few plugins bolted on to unify the UI, deployed in bulk. Over time the backends diverged, and here we are.
It's an difficult position Atlassian are inflicting on tens of thousands of customers. Atlassian's self-hosted products are uniquely flexible, being built on a plugin architecture, and many orgs have indeed customized Jira extensively with plugins, notably ScriptRunner [1]. Atlassian's Cloud plugins have their APIs, but have nothing like the same flexibility. A lot of functionality just isn't possible in the Cloud architecture. It's a bit like Firefox moving from XUL to an extension API.
In my opinion, the most customer-respecting way forward would be for Atlassian to open-source their discontinued Server product line. Go to the "open core" model with the clustered Data Center product as the upsell. This avoids screwing over their customers, and if their Cloud product really is as good as they say, customers will migrate to it naturally over time. It's the kind of damn-the-torpedoes move I think Mike CB would like.
But over the next 3 years, lots of painful migrating or evaluating-of-alternatives will need to happen, and perhaps a non-Atlassian forum for sharing experiences will help.
Just once, humming (not particularly well), not singing.
The song in question is sung with a very clear voice, with minimal instrumental backing. That may suggest the limiting factor is Google's ability to parse songs, rather than users' ability to hum them.
Gitlab is great for their developer niche, but the relatively weak issue tracker and wiki lets them down for more general use. Still, Gitlab is a great company with momentum and a roadmap. Feel free to join us [2] in looking at such alternatives.
[1] https://tempo-io.atlassian.net/wiki/spaces/THC/pages/8969584...
[2] https://www.goodbyeserver.org