3 ms·

I’m here.

• dreadlordbone 5y ago
  H-he's fast! Honestly the article is business focused but straight laced, seems like pretty good PR for Gitlab.
  • divbzero 5y ago
    > straight laced I agree. I suppose that’s a positive side effect of conducting business so openly. You’ll feel extra responsibility to set policies that are sensible not only internally but also to the general public.
• ethbr0 5y ago
  > 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?
  • john_cogs 5y ago
    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”.
    • ethbr0 5y ago
      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.
      • john_cogs 5y ago
        Good suggestion. Thanks. I documented it here: https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/-/issues/5826#note_815928634 https://gitlab.com/gitlab-com/marketing/corporate_marketing/...
  • boleary-gl 5y ago
    I like how meta this became and how many internal Slack channels are being discussed on HN
• gzer0 5y ago
  Impressive speed, John. And a hello to the Gitlab #hn-mentions slack channel.
  • john_cogs 5y ago
    Thanks.