While the CE version of GitLab will remain 100% FLO, GitLab.com just changed their ToS to add their integration of Pendo (some proprietary analytics, assistance, retention, telemetry product).
This is quite unfortunate in principle and for people who care about these things. It’s a potential sign of further compromises from them as they focus on getting profit.
Maybe wherever we mention our use of GitLab.com, we should mention this concern and suggest that people consider tools that block third-party requests, in this case presuming the scripts will be served by Pendo. I suppose it’s possible that GitLab will self-host the scripts, but the connection to Pendo should still be blockable.
I don’t actually care a lot specifically about this exact issue. I only care about what it means in terms of trust, principles, future concerns… I don’t like this sort of tracking norm that this is part of.
Since I haven’t yet posted the planned blog about us moving to GitLab.com, I suppose I should mention this as well, at least in a footnote if not more prominently.
Of course, everyone should be individually seeing their announcement email. Relevant quote showing at least better-than-typical caution from them: