Live data from Hacker News

Gitlab Handbook's HN Page

about.gitlab.com

51–60 of 200 posts

Re: Gitlab Handbook's HN Page

#51
post #28
post #24

Earlier quoted context omitted.

CEO is having dinner.

I think it's only you and Mr. Prince left from the IPO'd devtools crew, you're the only two I see still kicking around occasionally. But hey, big job so thanks for stopping by. Enjoy your dinner.

> IPO'd devtools crew

Is this a specific group rather than just devtool founders of IPO'd companies? HashiCorp founder Mitchell is still here: https://news.ycombinator.com/user?id=mitchellh

Re: Gitlab Handbook's HN Page

#52
post #47

Anyone else think this is a bit... icky? If you have to game the "system", sorry, I mean, provide "social media guidelines" to this extent, maaaaybe your [whatever you're trying to push/advertise/spread] isn't all that worthwhile...? Especially in the "nerd" world, it seems word of mouth will get out without having to rely on such inane strategizing. I understand that this is just the tip of the iceberg, and other co…

It would be foolish and self-destructive not to have such guidelines. Like it or not, social media such as HN can be crucial to company success.

Additionally, a lot of the rules on the page make it more likely that contributions to HN by Gitlab team members offer good community value.

Re: Gitlab Handbook's HN Page

#53
post #47

Anyone else think this is a bit... icky? If you have to game the "system", sorry, I mean, provide "social media guidelines" to this extent, maaaaybe your [whatever you're trying to push/advertise/spread] isn't all that worthwhile...? Especially in the "nerd" world, it seems word of mouth will get out without having to rely on such inane strategizing. I understand that this is just the tip of the iceberg, and other co…

I initially felt that way but less so as I read.

Also, any large company has procedures for PR. It’s a part of life.

Re: Gitlab Handbook's HN Page

#54
post #47

Anyone else think this is a bit... icky? If you have to game the "system", sorry, I mean, provide "social media guidelines" to this extent, maaaaybe your [whatever you're trying to push/advertise/spread] isn't all that worthwhile...? Especially in the "nerd" world, it seems word of mouth will get out without having to rely on such inane strategizing. I understand that this is just the tip of the iceberg, and other co…

How is it gaming the system to have clear guidelines that respect community rules and the spirit? Genuine question.

Re: Gitlab Handbook's HN Page

#55
post #47

Anyone else think this is a bit... icky? If you have to game the "system", sorry, I mean, provide "social media guidelines" to this extent, maaaaybe your [whatever you're trying to push/advertise/spread] isn't all that worthwhile...? Especially in the "nerd" world, it seems word of mouth will get out without having to rely on such inane strategizing. I understand that this is just the tip of the iceberg, and other co…

On the contrary, I think it's refreshing to see a company have policies that are appropriate and understanding of the community they want to be a part of.

Re: Gitlab Handbook's HN Page

#56
post #47

Anyone else think this is a bit... icky? If you have to game the "system", sorry, I mean, provide "social media guidelines" to this extent, maaaaybe your [whatever you're trying to push/advertise/spread] isn't all that worthwhile...? Especially in the "nerd" world, it seems word of mouth will get out without having to rely on such inane strategizing. I understand that this is just the tip of the iceberg, and other co…

Not really because:

1. Other companies probably have similar strategies but it's behind closed doors to act however nefarious they would like, not open docs that can be criticized here publicly like Gitlab has.

2. The MO (modus operandi) here seems entirely about reading customer feedback and engaging with it. That's like YC startup advice numero uno. They explicitly mention not to submit content or get people to upvote.

Re: Gitlab Handbook's HN Page

#57
post #11

Earlier quoted context omitted.

I’m here.

> If a notification that a release post has reached the Hacker News Front Page is posted to the #developer-evangelism Slack channel by the "Hacker News Front Page" bot, a Developer Evangelism team member should quickly repost the message to the #product and #release-post channels to alert our Product Managers. Why doesn't someone just update the bot to post in those channels as well?

I like how meta this became and how many internal Slack channels are being discussed on HN

Re: Gitlab Handbook's HN Page

#58
post #28

Earlier quoted context omitted.

I think it's only you and Mr. Prince left from the IPO'd devtools crew, you're the only two I see still kicking around occasionally. But hey, big job so thanks for stopping by. Enjoy your dinner.

> IPO'd devtools crew Is this a specific group rather than just devtool founders of IPO'd companies? HashiCorp founder Mitchell is still here: https://news.ycombinator.com/user?id=mitchellh

Oh yeah, I forgot about Mitch, although I don't see him around that much, sytse and eastdakota I see quite frequently. Also apparently Jeff Lawson is still active(ish)! https://news.ycombinator.com/threads?id=jeffiel

Will be interesting to see if, once stripe goes public Patrick sticks around.

Re: Gitlab Handbook's HN Page

#59
post #9

> Never submit GitLab content to Hacker News. Submission gets more credibility if a non-GitLab Hacker News community member posts it, we should focus on making our posts interesting instead of on submitting it. I appreciate this policy, it makes it clear that HN is a place to engage with the community, rather than a free advertising channel. Looking at the CEO's profile, the last time he made a submission about Gitla…

In my ideal world, most content sharing and even social media sites should be like this. Good content driving interest instead of gaming the algorithm to get clicks and views would lead to a better ecosystem of information with less noise.

Although I doubt we’ll ever reach that point so I’m wondering if there are other small communities around the web that are just more quality-oriented on the content shared (I just go to niche subreddits and mostly HN)

Re: Gitlab Handbook's HN Page

#60

Hey there, I’m a member of the GitLab Community Relations team. My team is responsible for this page. I shared the page today at a DevRel meetup where OP was presenting on Hacker News. I’m grateful he chose to share it with all of you. Thanks, Dan. If there are ways we can improve how we engage with the HN community, myself and our team would love your feedback.

One thing that looked a little odd is the doc asks potential contributors to familiarize themselves with a fairly convoluted guide to 'unofficial' HN features but doesn't mention or link HN's own guidelines and FAQ. But maybe it's targeted at people who've read them?
Post reply on HN