61–70 of 285 posts
The real reason you shouldn't be using GitLab is performance. How is it possible that that page took over a minute to load? Nevermind that the design is completely incomprehensible.
further down the thread are mentioned of ruby on rails. i use gitlab because it allows me > 1 private repo. if there are better solutions then i'm all ears.
Is this supposed to read "misunderstands"? And if not, could you elaborate?
I don't see where it is canceled. The closest thing I see to canceled, is postponed. From the update: 'We will not activate user level product usage tracking on GitLab.com or GitLab self-managed before we address the feedback and re-evaluate our plan.' That leaves a lot of wiggle room.
I’ll reserve the pitchforks for if this comes up again.
However, given that most of the Gitlab customers / open-source community cares about their privacy and want to have the control (well, that's probably why they switched to Gitlab from other products), I wonder why they wanted to follow this approach in the first place. The good thing is that they almost always know how to take action when their community reacts.
Earlier quoted context omitted.
further down the thread are mentioned of ruby on rails. i use gitlab because it allows me > 1 private repo. if there are better solutions then i'm all ears.
Have a look at GitHub. It's a similar service with unlimited private repos for free.
Earlier quoted context omitted.
Most of everyone's main reason was that GitLab was "open source" and also supports free software. As much as they claim to do, I'm afraid that by being partially owned by VCs, they are at the mercy of pleasing those who may conflict with these ideas in favour of adware such a telemetry or ad-tracking. A very principled move from GitLab to revert this, but I think that GitLab's trusted is damaged due to this.
I think it will bring them under more scrutiny and rightfully so. But this sounds like a misunderstanding, both of the GDPR and user sentiment, enforced without discussion from the top. They responded quickly, humbly, and transparently in reversing the decision. I'm not sure about long-term erosion of trust, although this may harm subscription levels or contract negotiation in the medium term
Earlier quoted context omitted.
Even anonymous cohort analysis can be super useful as a product manager. If you want to encourage usage of a particular feature and the most successful users of that feature fit into a cohort, you can reach out to them for feedback, optimize paths between those features, improve documentation connecting relevant features together, etc. This doesn't mean its malicious or all about the $$$...it might be that users that…
That's an interesting point. But wouldn't the vast majority of Gitlab users be signed in (and thus server-side trackable)? Pretty much all functionality other than just reading code seems to require it.
* Gitlab previously used 3rd party infrastructure for their user event tracking
* They did not send this 3rd party user id for GDPR and other reasons
* Because they did not have user id, they could not understand user behavior across sessions. Understanding user behavior across sessions is important, so they wanted to add it.
* Gitlab had just finished moving their event tracking infrastructure in house.
* The original MR was to add user id as an attribute to their event tracking
What proceeded was what I consider a very reasonable back and forth between data, infrastructure, and legal on the correct way to add user id. But somewhere along the line it went off the rails. How it turned from simply adding user id into including Pendo JS tags for on-prem customers, I have no idea.
The reaction to this whole saga has been insane. Chill out people. They fucked up, users gave feedback, they listened. This isn't some corporate conspiracy, some grand ethical dilemma with an evil company on one side and some white knight hackers on the other. Let's imagine for a second that they are people trying to do the right thing, with years of history doing the best they can. They wanted to measure usage to ma…
EDIT: https://gitlab.com/gitlab-org/gitlab/merge_requests/14182#no...
The reaction to this whole saga has been insane. Chill out people. They fucked up, users gave feedback, they listened. This isn't some corporate conspiracy, some grand ethical dilemma with an evil company on one side and some white knight hackers on the other. Let's imagine for a second that they are people trying to do the right thing, with years of history doing the best they can. They wanted to measure usage to ma…
What's great with GitLab compared to other companies is that they are doing things in the open, while another company would just violate my rights without me knowing it.
If you go through the comments, multiple (toxic) people in GitLab doesn't care about user rights, just want to push the change as soon as possible (just like in any other company that I have been working in).
It's also clear that you get VP/Director/Staff engineer by just pushing through other people (sadly I have seen the same thing happening other times as well).