I wish more places adopt this culture.
Gitlab Handbook's HN Page
41–50 of 200 posts
Re: Gitlab Handbook's HN Page
#42Earlier quoted context omitted.
> 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?
Many of the posts that reach the front page are simply posts that contain GitLab in the URL (ex: a link to an issue from an open source project hosted on GitLab). Others are only relevant to specific teams. My team handles directing the posts to the right folks to avoid unnecessary distractions from “false positives”.
What about about.gitlab.com/releases/* ?
Not trying to belabor the point, and I'm sure there are nuances (especially with blog posts), but releases seem (a) likely to continue forever & (b) to use well-formed URLs.
Re: Gitlab Handbook's HN Page
#43Re: Gitlab Handbook's HN Page
#44GitLab's been good for our company, having it all under one roof has been nice.
But recently I've had (and continue to have... still not resolved) a pretty unpleasant experience with their support software. It just seems like the typical comedy of errors where a series of software integration papercuts between them and Zendesk adds up to a really bad experience, made much worse by the fact that our issue hasn't been fixed which is making us more stressed.
I am a member of multiple Gitlab groups and owner of one. I am simply not able to log in to the support portal to leave a ticket. Then I replied to a zendesk ticket and then somehow I get this message about support entitlement. I mean why not just speak in English? Why use terms like "Support Entitlement" – just say, which org/group are you with? Or just look me up in your database. An email address is unique. So that's confusing.
This roundabout has caused us to spend days and days just to reactivate an account that was locked out due to 2fa (not Gitlab's fault). We haven't even gotten to actually solving the problem. We're stuck on basically "I don't know who you are from your email address so you need to tell me who you are" even though I'm using the owner email address for that account.
I'm sure Gitlab's support TEAM must be great, but it fails spectacularly due to what seems to be flawed Zendesk Gitlab integration itself. Please fix this guys, I know you're on top of everything else. It just feels like a forgotten set of tools.
Why can't I just SSO using my GitLab credentials into Zendesk?
Re: Gitlab Handbook's HN Page
#45This is very meta
Re: Gitlab Handbook's HN Page
#46> We learned that the key to a post reaching the front page was the content itself.
Content is King.
Re: Gitlab Handbook's HN Page
#47Anyone 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 companies/orgs likely have similar strategy pages, but it all seems a bit, i dunno, anti-HN to me.
Re: Gitlab Handbook's HN Page
#48Earlier quoted context omitted.
Many of the posts that reach the front page are simply posts that contain GitLab in the URL (ex: a link to an issue from an open source project hosted on GitLab). Others are only relevant to specific teams. My team handles directing the posts to the right folks to avoid unnecessary distractions from “false positives”.
What about about.gitlab.com/releases/* ? Not trying to belabor the point, and I'm sure there are nuances (especially with blog posts), but releases seem (a) likely to continue forever & (b) to use well-formed URLs.
Good suggestion. Thanks. I documented it here: https://gitlab.com/gitlab-com/marketing/corporate_marketing/...
Re: Gitlab Handbook's HN Page
#49GitLab's been good for our company, having it all under one roof has been nice. But recently I've had (and continue to have... still not resolved) a pretty unpleasant experience with their support software. It just seems like the typical comedy of errors where a series of software integration papercuts between them and Zendesk adds up to a really bad experience, made much worse by the fact that our issue hasn't been…
Thanks, I’ve shared this feedback with members of our support team.
Re: Gitlab Handbook's HN Page
#50Anyone 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 may seem icky but I think once a company hits a certain size it is important to define some basic rules for external communication of any type, otherwise it becomes a garbled mess.
Overall the policies seem pretty common sense and hands off which is good! Hopefully this community is robust against astroturfing (something I'm worrying about with Reddit)