Funny how they don't seem to really have any non-specialised tools to coordinate, manage and track work in a structured way across the company (like smaller team tools like Trello, or larger ones like Asana). The only cross company collaboration tool I saw on that diagram was Slack!
Every software system used at Gitlab
101–110 of 123 posts
Re: Every software system used at Gitlab
#102Earlier quoted context omitted.
Sorry that this happened. We still have a long way to go to improve our billing system. We have allocated more people to it since a few months and are making much faster progress. But it isn’t we’re it should be at the moment.
Thanks. No worries, these things happen. It's just a little alarming to see messages like "we've downgraded you to the free plan". Even a bit of help text in the banner, linking to a page on situations under which the message might be raised / not be 100% accurate, might ease the experience.
Re: Every software system used at Gitlab
#103As a complete remote company, I wonder if GitLab's business affected much by COVID-19?
Those with kids, I know that it can be even more challenging or exhausting. so in some ways "unaffected" in others "feeling it". Pretty much like everyone else.
I can't comment specifics on finances, but I do count my lucky stars that GitLab raised when it did as it personally gives me a little more reassurance that we may be less affected. That said, obvs anything can happen to me or GitLab.
Re: Every software system used at Gitlab
#104Curious about whether Salesforce represents a single point of failure. If it goes down or is unavailable, what impact does that have on the rest of the organization?
We listened to the lesson and the architecture we designed ended up not having Salesforce as a dependency for any critical or money producing customer facing functionality.
We used Alteryx as a ETL tool to keep Salesforce in sync in almost real time. The customer facing sites and services ran off their independent databases. This also meant that the developers working on that didn't need to know the details about how Salesforce worked, we just mapped Salesforce data to their database.
Re: Every software system used at Gitlab
#105Earlier quoted context omitted.
For huge diffs, there’s not much that beats `git checkout && git diff HEAD^`. For leaving comments, pretty much every system I’ve used has issues. At work we use phabricator; the default settings are atrocious but they can be tuned to something workable. I sometimes wonder how hard it would be to get diff reviews to be a first (or even second) class citizen of the git ecosystem. That way you can finally get the bliss…
> [git ecosystem] have “notes” which are vaguely similar, maybe it’s something they’re considering? If you're referring to git-notes, they are ... kinda special. They are objects in their own namespace that reference the repository objects the notes themselves are attached to. Sure enough, you can attach a note to any git-object. And you can view them either directly or from the git-log view. But the discoverability…
I was meaning to point out that we've developed plumbing for objects with "weaker" guarantees than source code, which can still be attached to refs. To me, this is indicative that the maintainers are willing to accept patches on things that are outside the "core mission" of versioning source code, and might mean that they're open to the idea of accepting a well-architected code review feature.
Although, you're also right, in that there's still a lot of plumbing to make sure that authors can only edit their own comments, and that sort of thing. The more I think about it, there's a lot of work to be done and it isn't easy.
But, if you made a proposal, I think git-notes is precedent for them accepting your contributions. :)
Re: Every software system used at Gitlab
#106We've just had a bad experience with GitLab annual renewal, to the point where we didn't know if they'd cancelled our account or not. The billing accounts system seems to be completely disconnected from user accounts. A notification banner was spammed to users in the GitLab.com user interface, saying that our account was going to be cancelled becuase we didn't have auto-renew. The users who got the banner didn't have…
0. https://gitlab.com/gitlab-org/gitlab/-/issues/3320#note_3351... 1. https://about.gitlab.com/handbook/ceo/pricing/#reporter-user...
Re: Every software system used at Gitlab
#107We've just had a bad experience with GitLab annual renewal, to the point where we didn't know if they'd cancelled our account or not. The billing accounts system seems to be completely disconnected from user accounts. A notification banner was spammed to users in the GitLab.com user interface, saying that our account was going to be cancelled becuase we didn't have auto-renew. The users who got the banner didn't have…
I'm not surprised. They currently refuse to have a sane policy around licensing people who just want to put in issues and view repos vs actual developers. They make all users count as a full developer, which makes no sense. Their reasoning is basically "its just easier for us" which is not the point. [0][1] 0. https://gitlab.com/gitlab-org/gitlab/-/issues/3320#note_3351... 1. https://about.gitlab.com/handbook/ceo/pri…
But that said, I do wholeheartedly agree! The top-tier account type allows free reporter-level users. But for every other tier (e.g. silver), you have to pay for them. I think that's big mistake, as the cost-benefit of paying 200 USD per year for each member leads to work-arounds, which compromises the user experience.
Re: Every software system used at Gitlab
#108I'm so sick of Gitlab support spam in every thread that mentions any issue, making it so that critical conversations are interrupted with self serving pitches! >I once saw Gitlab do this thing. >Hey, Bob from Gitlab thing here. We are really trying to make thing great for our customers . Our next release of thing will do foo which we hope will fix this. Here is a link to a marketing post comparing us to GitHub. Hope…
Re: Every software system used at Gitlab
#109Re: Every software system used at Gitlab
#110Gitlab has been pretty great so far, but the code review tooling is so poor I think I need to look elsewhere. The pull request pages take forever to load, they can't handle pull requests with over 800 lines well at all. It will collapse files with over 100-200 lines of changes for seemingly no reason (hiding the comments within them). You can't ignore whitespace in diffs, and the comments disappear from the diff if t…
I don’t understand. This describes basically every code review tool I’ve ever used. If there’s something aside from Gitlab that I should try that still integrates, I’d love to know.