[0vermorrow]

The pushback from users made them rethink this change, here's a pending merge request to the blogpost: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...

""" UPDATE: Thanks for the feedback. There were many more concerns than we expected. We’re going to process the feedback and rethink our plan. We will not activate product usage tracking on GitLab.com or GitLab self-managed for now. We'll make sure to communicate in advance on our blog when we do have a new plan. """

[ianamartin]

You can tell a company has totally lost their heads up their asses when you get the, "Whoa! We totally weren't expecting <product decision> to upset so many people!"

Like really? Considering what people use your product for, you honestly didn't expect this to upset people? Great. Your product team is hopelessly out of touch.

[mumblemumble]

That statement is for PR purposes; you can't take it at face value. Let me attempt a translation into plain English:

"I, personally, totally expected this, as did everyone who I talk to on a daily basis. But someone up the chain of command thought we could get away with it, and forced us to try and push this change. I'm going to use the pronoun 'we' to refer to the company in the abstract, and not anyone on the immediate team I work with, because I jolly well can't be throwing my boss's boss, who happens to also be a commisar from the large company that recently acquired us, under the bus."

[jahlove]

> But someone up the chain of command thought we could get away with it

That person is Paul Machle (CFO):

"I don’t understand. This should not be an opt in or an opt out. It is a condition of using our product. There is an acceptance of terms and the use of this data should be included in that." [1]

[1] https://gitlab.com/gitlab-org/gitlab/merge_requests/14182#no...

[hn_throwaway_99]

Ouch, that whole thread under there is painfully oblivious:

> @cciresi if we follow Paul's guidance and just make this part of our terms and conditions, are we covered legally?

Earth to GitLab: You are not yet big enough to be at the "are we covered legally" stage. You are toast if that is your mindset.

[ryandrake]

When someone raises an ethical question and instead of addressing ethics, the company calls in the lawyers to address whether it's legal... your company is likely on the wrong track.

[elliekelly]

To be fair I’d say half the time I’m summoned into a discussion like that it’s because the person asking fully expects and wants me to say no to the proposal. Raising an issue with the plan of action set forth by someone more senior can be tricky to navigate politically.

[rhizome]

AKA "well it's not illegal," a lousy lower-bound.

[dboreham]

Having been in a few of these kinds of discussions inside companies, it's super-fascinating to find one that is open to the public! It shows what is always true: that any "corporate decision", seemingly made by some sort of AI machine, was actually made by one specific (usually unidentified) person. Popcorn moment for sure.

[lovehashbrowns]

Man, that reply in particular left the biggest impact on me. The fact that this c-level exec is making decisions like this in such a ham-fisted way would scare me away if I were a customer. There are a chain of repercussions as a result of this.

[antisemiotic]

Twelve thumbs down and one middle finger. (I'm not a native speaker of emoji and I'm not sure what the 8 ball means). These are from employees?

[sicromoft]

Sure, but that just changes it to "someone up the chain of command is hopelessly out of touch". Still doesn't bode well.

[6031769]

Which large company was it that recently acquired GitLab Inc.? I must have missed that.

[mumblemumble]

Nah, you didn't. I was mistaken - I thought I had read something about that recently, but it looks like it's just that they raised another round of funding last month.

[juped]

Funding rounds are changes in ownership structure.

[woadwarrior01]

I suspect the think was more along the lines of: let's slip it in and hope nobody notices or at least the ones that notice don't raise a hue and cry about it.

And now that it's turned out to be false, the dominant strategy is to offer a half apology along the lines of "We're sorry, we didn't expect that it'd be such a big deal".

Incidentally, it's quite reminiscent of the Grace Hopper quote: "It's easier to ask forgiveness than it is to get permission."

[DoofusOfDeath]

> "It's easier to ask forgiveness than it is to get permission."

When people use that quote, I try to be charitable and assume that they don't intend its literal, face-value meaning.

But if they do, my response is: I will not forgive you because you're not truly repentant. This is all part of a strategy where you see what you can get away with, and you show no signs of repenting that overall strategy.

Hmmm... maybe I'm a hardass.

[Aeolun]

I don’t think that really applies to companies that are still living by the grace of their popularity.

Gitlab is heavily dependent on developers pushing their product to the enterprise, because any executive would be far more happy with Atlassian (e.g. cheap and it works)

[cryptonector]

> I suspect the think was more along the lines of: let's slip it in and hope nobody notices or at least the ones that notice don't raise a hue and cry about it.

"let's slip it in and hope nobody notices" == "mgmt heads up their asses"

[rhombocombus]

That places them on the "companies I probably wouldn't be happy working for" list. Certainly there are folks there who tried to speak up about it who were likely railroaded.

[swozey]

That's the vibe I get on just about every one of Gitlabs new screed posts on here recently. Hopefully there actually is some employee consensus on decisions, though.

[Kalium]

As a rule, the structures around product teams tend to discourage asking if it's better to not ship a thing. When you measure a team by what (and how many things) they ship, they are always going to default to shipping things.

[overgard]

The structure thing is spot on. Decisions like this tend to get made when management has found a way to essentially silence any feedback (by making feedback pointless). This is why I cringe whenever I hear the phrase "leadership team". Whenever I hear that phrase deployed it's almost always to diffuse responsibility for a bad decision so no single person has to answer for it. Which amusingly is the opposite of real leadership: real leaders actually accept responsibility for the decisions they make.

[hn_throwaway_99]

This is absolutely true. It's absolutely what killed Digg with Digg V4 IMO.

I can't possibly believe anyone who ever used Digg could have taken a look at Digg V4 and thought "Oh yes, a feed full of spam, just exactly what I come to Digg for". But the team had already invested a ton of work, and organizationally it would have been next to impossible to say "Shit, we fucked up, lets hold off". So at least I give GitLab credit that they backed off (for now).

[LyndsySimon]

This is... insightful.

It brings to mind a larger question of how we (as an industry) should be measuring developer and team productivity, though. “Story points” are largely designed to solve this issue, but in my experience they are quickly co-opted to mean something different to each stakeholder.

At a past employer, I experienced their trying to measure productivity by “net lines of code”. That didn’t work well, either. I prefer refactoring and simplifying to pretty much any other type of task, and it isn’t at all uncommon for me to end a day - or a sprint - with a negative NLOC. I see at a positive, as each LOC carries with it an ongoing cognitive and maintenance burden. Thankfully, that scheme didn’t last long :)

[kevas]

This is hitting too close to home. Currently on a team that does what’s on the task list without questioning anything—driving me up the wall.

[Aeolun]

This is a function of the organization, not the team.

If you hear ‘do it anyway’ after raising concerns one too many times, eventually you just do it.

[JohnFen]

Not necessarily. It depends on exactly what "it" is. I have quit jobs before because I was required to implement something that I considered an egregiously terrible idea.

[Juliate]

Sounds pretty standard operating procedure for product teams in large software companies, actually.

Sad. But systemic to the industry.

[Rapzid]

Some bonehead got in charge and forced this through. People were screaming internally but ignored as trouble makers. So it goes.

EDIT: To clarify, I'm just making a generalization and am not affiliated with Gitlab.

[Sir_Cmpwn]

This language is the classic "defuse, wait, and try again later" approach to shoeing in unpopular changes. They're still hedging their bets with this language, rather than renouncing the original ideas. Apologising for "bad communication" instead of bad changes is another classic deflection move they've pulled in other threads, too.

<disclaimer: founder of a GitLab competitor>

[mwcampbell]

> <disclaimer: founder of a GitLab competitor>

IMO, if you want to compete with GitLab, you should introduce some higher pricing tiers targeted at businesses. These should be comparable to GitLab's pricing tiers and should not have "hacker" in their names. I also suggest that for these higher pricing tiers, you make it explicit that using the service for closed-source projects is OK.

[Sir_Cmpwn]

This is good feedback, but I think the bigger issue is the alpha quality of the service. People who move now will have to be tolerant of some pieces being missing or under-documented, which often means a vote of confidence in the future of SourceHut more so than in the present. When the alpha becomes the beta, and then production, the pricing model will be re-evaluated.

[Aeolun]

Ideally, price it at the $20/month/person price that Gitlab has, because that seems to be the highest that I’m able to sell to Management.

Theoretically $100/month/person would still be a great deal, but the finance people don’t look at it like that. They just see the $97.5/month/person difference with Bitbucket.

[rvz]

> There were many more concerns than we expected.

Telemetry was always going to be a concern with services that promote themselves as "open-source" or "free-software". The subject is so important that it is one of the reasons that the mass exodus from GitHub to GitLab happened. So to say that "there were many more concerns than we expected" is complete bullsh*t and appears more like the VCs are puppeteering the founders with this talk here.

Like other companies that are at the mercy of VC funding, they will do anything to please them over the "community" to show that they are growing. So don't be fooled by this empty response.

[matheusmoreira]

Because of their fiduciary responsibility, the officers of a corporation must make decisions that increase shareholder value. Refusing to add profitable data collection to the product due to ethical concerns would be a violation of that duty to the investors.

This will keep happening until it literally becomes illegal to collect personal information.

[rswail]

This is a corporate lie that has been promoted relentlessly since the Reagan era. Officers of a corporation are responsible for the operation of the corporation in accordance with the law.

They are responsible to the Board of Directors of the corporation, not the shareholders. The Directors are responsible to the shareholders.

They have a responsibility of care (including a fiduciary responsibility) to operate the corporation in the corporation's best interest, not the shareholders, as directed by the Board.

That best interest can be measured in all sorts of ways as established by the Directors, which may include increasing shareholder value.

The practise of CEOs also being the Chairman of the Board, of executives being major shareholders, of bonuses being driven by share price, are all practises that should be eliminated, given that they are not in alignment with an executive's actual responsibilities and duties.

[Aeolun]

> Because of their fiduciary responsibility, the officers of a corporation must make decisions that increase shareholder value.

Drilling a hole in your ship may be immediately helpful because you are thirsty, but ultimately it’s not going to end well for you.

I’d say it’s well within the realm of reason to say a hard ‘no’ to investors in this case.

[dorian-graph]

> There were many more concerns than we expected.

So they expected some, but still went ahead anyway?

[skywhopper]

There will always be concerns and complaints. I'm more surprised they didn't expect a firestorm given the way they explained the change, though. I wonder how many people actually reviewed the language.

[jcims]

Nothing wrong with that in general, you can't make everyone happy.

[toflon]

There will always be concerns from some people. Always.