161–170 of 201 posts
It used to be the default that self hosted apps didn't telemetry and call home.
I feel there's more than one self hosted foss jira alternative around already, that of course wouldn't telemtry or call home.
Some I used in the past:
https://phacility.com/phabricator/ no longer maintained :-(
After a U.S. federal contractor told us they loved Plane but couldn't use it due to ITAR requirements, we spent 6 months building a truly air-gapped version. No external connections, no license pings, no telemetry, everything runs in complete isolation. The interesting part: our air-gapped deployment actually runs faster than our SaaS version. Turns out when you eliminate all network latency, things get snappy. This…
> The interesting part: our air-gapped deployment actually runs faster than our SaaS version. This is the least surprising thing I’ve read all day.
Earlier quoted context omitted.
If they also realize that having less dependencies makes deployment easier we have gone full circle.
I can't believe how many devs think dependancies are completely cost free...
After a U.S. federal contractor told us they loved Plane but couldn't use it due to ITAR requirements, we spent 6 months building a truly air-gapped version. No external connections, no license pings, no telemetry, everything runs in complete isolation. The interesting part: our air-gapped deployment actually runs faster than our SaaS version. Turns out when you eliminate all network latency, things get snappy. This…
> Turns out when you eliminate all network latency, things get snappy. Same experience with JIRA. I read all these negative comments here and elsewhere about how slow and clunky JIRA was, and I couldn't relate at all. Then I realized all those who complained was using JIRA Cloud and we were using on-prem, and it all made sense. We've since moved to JIRA Cloud ourselves, and I understand now. We moved and none of the…
The annoying part is the amount of garbage fixes in JIRA's UI. For example, because of the loading speed, and me losing patience with it, if I don't wait for the page to finally finish loading and click on the "create" button, then instead of the modal dialog for issue creation, I get a whole new page for issue creation. Both options are atrocious from UX perspective (because usually I need to copy text from the issue I was reading into the issue I'm creating), but at least when it's a modal window, I can pop open the developer tools and delete the modal part that prevents me from copying the text from the issue otherwise blocked from interaction.
Also, it looks like due to speed, some queries simply don't finish on time, and randomly, searches don't find all the issues they should. Especially searches that ask for "s.t. parent issue has such-and-such properties".
Ultimately, JIRA isn't built to scale (ironically, since it's written in Java, which was always defended as being slow for small problems but scaled well). The code has a lot of assumptions about some operations being fast enough to not require buffering / incremental implementation. And sometimes you hit the combos of such unoptimized operations and have to wait minutes for the program to respond.
A truly airgapped Jira-alternative would be somewhat impractical.
After a U.S. federal contractor told us they loved Plane but couldn't use it due to ITAR requirements, we spent 6 months building a truly air-gapped version. No external connections, no license pings, no telemetry, everything runs in complete isolation. The interesting part: our air-gapped deployment actually runs faster than our SaaS version. Turns out when you eliminate all network latency, things get snappy. This…
> Turns out when you eliminate all network latency, things get snappy. Same experience with JIRA. I read all these negative comments here and elsewhere about how slow and clunky JIRA was, and I couldn't relate at all. Then I realized all those who complained was using JIRA Cloud and we were using on-prem, and it all made sense. We've since moved to JIRA Cloud ourselves, and I understand now. We moved and none of the…
Out of the box it is pretty generic. When I learned what it could actually do, it revealed itself as a sponge that can uniquely absorb complexity. Having someone familiar with JIRA show the ropes went a long way.
Some of these new development tools are pretty nice though. Variety is good, especially with the changes from Pivotal Tracker, etc going away.
"air-gapped" self hosted app. It used to be the default that self hosted apps didn't telemetry and call home. I feel there's more than one self hosted foss jira alternative around already, that of course wouldn't telemtry or call home. Some I used in the past: https://www.redmine.org/ https://phacility.com/phabricator/ no longer maintained :-(
I haven't used Phorge, but Phrabricator is easily my favourite tool among the source code portals. The code review system actually works and does not make me tear my hair out. I am completely at a loss why the commercial side of it seemingly failed after all those years, when products such as Bitbucket and Gitlab seem to do well.
Earlier quoted context omitted.
> Then I realized all those who complained was using JIRA Cloud and we were using on-prem, and it all made sense. Even Atlassian doesn't use Jira cloud. Btw it's not "JIRA".
What a weird time to enforce British rules for acronyms. JIRA stands for JIRA Isn't Really Awesome.
Earlier quoted context omitted.
> The interesting part: our air-gapped deployment actually runs faster than our SaaS version. This is the least surprising thing I’ve read all day.
If they also realize that having less dependencies makes deployment easier we have gone full circle.
(presumably read in Adam Something's voice)