131–140 of 205 posts
Earlier quoted context omitted.
I would say using on-prem products and never updating them because of penny pinching is much bigger business risk.
What business risk does that incurr?
I stayed at a hotel that was having a massive cloud outage and I couldn't get my room key at check-in. That night I had dream that on-prem became the new cloud. State was beautifully synced with CRDTs. In this dream, systems never went down, the data just became temporarily stale. Then I woke up.
The problem with Jira is that we don't have many alternatives at enterprise level. Maybe for smaller teams ( I had a lot of hopes for Github Issues [0] but since they announced the product on last year's Universe event, there were not many news. Maybe this November they will come back with an update. At this point, I feel Jira is like WordPress. It maybe slow and overbloated, but you can have absolutely any plugin an…
Earlier quoted context omitted.
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…
How is the product so terrible that running a 100 person instance is a pain in the ass?
Earlier quoted context omitted.
Not OP, but we moved to Gitlab Issues. Project Managers are missing some features, but the devs (including me) like it a lot more due to integrating so well with PRs/commits.
The problem with this though, is that commonly a requirement (ticket) does not map exactly to a single code repository. I feel that it is breaking encapsulation in a sense to be dealing with issues at the repo level. The repo and the code are implementation details of the business requirements. The tickets describing requirements belong at the next level up of abstraction?
Last year I was second guessing myself if migration to Gitlab EE from Jira, Bitbucket and Jenkins would be worth it, as it was a massive shift for my org. Maybe purchasing a DC version of Atlassian products would be a better alternative, but after short look into invoices and licensing it was decided to go forward with Gitlab. Still not a big fan of how stiff Yaml pipelines feel in Gitlab CI and that tickets for what…
Plus, the cost of gitlab is getting insane. It's very hard to justify the jump, no matter how worth it is. Jira "just works" for now, and honestly it wouldn't surprise me if gitlab raises their pricing even further. (which I totally understand, they are not profitable yet and have to do a lot of work. It's just that it sucks having to be cautious about who gets access to your instance since you can't have multiple ti…
Earlier quoted context omitted.
Not OP, but we moved to Gitlab Issues. Project Managers are missing some features, but the devs (including me) like it a lot more due to integrating so well with PRs/commits.
Project Managers might just need some training. The board system in GL is very flexible and adaptable to how your org works. I was really impressed.
Earlier 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".
Has anyone identified an easy/feasible way to add SSO authentication to github pages?
Have the GH Pages (sub)domain proxied with CF, protect the URL with Zero Trust, for SSO itself there are several IdP available [0]. First 50 users are not billed.
[0]https://developers.cloudflare.com/cloudflare-one/identity/id...
Earlier quoted context omitted.
Project Managers might just need some training. The board system in GL is very flexible and adaptable to how your org works. I was really impressed.
YAY! I work on planning features at GitLab and Gabe from my team put together this overview view if any of you want something you can share with your team for training https://www.youtube.com/watch?v=KmASFwSap7c . You can also find agile planning tutorials in our docs site https://docs.gitlab.com/ee/tutorials/plan_and_track.html
Earlier quoted context omitted.
Not gonna happen unless a new server OS arrives that's significantly easier to use than Linux. The core diff between on-prem and cloud isn't where the data is hosted. It's that in one case someone else handles UNIX BS and in the other case you do. Get a MacOS-equivalent level of usability for servers in a form that isn't rent it by the hour, and you could see such a migration, but what's the incentive for anyone to b…
Curious what you see as the "UNIX BS" in running a server? Is it the need to CLI? Or just the number of knobs that you can frob? Too many choices? Interested in how such a server system might look.
To compare, try comparing the docs and GUI help you get deploying a simple serverless app to Lambda+RDS vs configuring a Linux box with systemd, apache/nginx, SSL termination, postgres, borgbackup or whatever other stack you want to use. The difference is night and day. The systemd docs alone are classic Linux BS culture. UNIX sysadmin is complicated in very fundamental and deep ways for people who don't have a gray beard. I know how to do it but I don't enjoy it, and I had to recently teach a friend of mine how to do basic tasks. He's a pro software dev with years of experience incl at Google but sysadmin was never something he needed to do. Luckily now ChatGPT can help a lot with the missing usability.