Live data from Hacker News

Viewing profile — emilycook

emilycook

HN member
Joined
Thu, Nov 15, 2018, 4:24 PM UTC
HN karma
229
Public activity
146 items

About emilycook

Sr. Community Program Manager @ CircleCI

Recent public activity

  1. comment
    Comment #27978383

    Hey I'm the Community Manger at Mattermost, if yall do build the integration and need any help with anything, feel free to reach out to me (emily.cook@mattermost.com) or join our c…

  2. comment
    Comment #27978045

    I'm not that familiar with Flowdeck so I don't know if this is what you mean, but "collapsed threads" in Mattermost is just a personal view setting that can be turned on/off accord…

  3. comment
    Comment #27974914

    I work at Mattermost -- we do have this, it's just still in beta right now https://docs.mattermost.com/messaging/organizing-conversatio...

  4. comment
    Comment #27029959

    The Mattermost team is working on automating feature testing of the webapp to 1. Decrease time to ship a bug fix release 2. Raise the quality of the software by reducing number of …

  5. story
  6. comment
    Comment #26556281

    Hey there, I work at Mattermost and would be happy to help with anything regarding an integration. If you're planning on this I would encourage you to join our community server: ht…

  7. comment
    Comment #23837775

    Yes, if the support ticket is opened when the issue is discovered. This particular instance was first reported on hackernews and was due to our dormant namespace policy: https://ne…

  8. comment
    Comment #23832964

    We clearly outline what we consider dormant here: https://about.gitlab.com/support/#dormant-namespace-requests It's to prevent name-squatting, GitHub has a similar policy: https://…

  9. comment
    Comment #23832926

    For future reference, you can see what we consider dormant here: https://about.gitlab.com/support/#dormant-namespace-requests

  10. comment
    Comment #23832798

    I wouldn't worry about that, we have clear conditions that need to be met before we release a username [1]. It's meant to prevent name-squatting, not take usernames away from actua…

  11. comment
    Comment #23382757

    We do have a performance team who is working on continuously improving the speed, so hopefully that is improved in the future! https://about.gitlab.com/handbook/engineering/perform…

  12. comment
    Comment #23303665

    I work at gitlab and just stumbled across this, we use U2F but we have an MR to add WebAuthn support https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26692

  13. comment
    Comment #23275443

    oops misspoke and now I can't edit, I meant deployment of applications to AWS (hopefully you knew what I meant!)

  14. comment
    Comment #23273536

    Hi! There are a lot of new features with this update, so here are a few highlights: -improved version of Gitaly service called Gitaly Cluster for high availability git storage [1] …

  15. comment
    Comment #22878964

    Oh my goodness thank you so much for this! I'm gonna show this to our performance team. I appreciate you sharing the comparison, this is very helpful.

  16. comment
    Comment #22878615

    Oh no I agree, that was just a comment recognizing that my experience is different because I'm in a more ideal situation than other developers are surely dealing with. I still pass…

  17. comment
    Comment #22878537

    Thank you so much for the feedback! I'm asking around to see if there are any projects open to reduce the number of pages, but I do know for sure that reducing page load times is a…

  18. comment
    Comment #22878086

    Thanks for the feedback! It's funny you mention the Auto DevOps documentation because we just had our new senior tech writer pick up an issue [1] to completely redo it, so hopefull…

  19. comment
    Comment #22878030

    Thanks for the feedback! I passed it on to our content team to see if they want to make adjustments to the blog post. I definitely don't want it to come across as misleading.

  20. comment
    Comment #22877986

    That's interesting feedback, I'll pass it along to the product team, although this is an angle they've probably thought about more than I have. The way we use it isn't really as an…

  21. comment
    Comment #22877659

    Hey! GitLab employee here. The speed of the site has been on our radar too, we have a handbook page [1] detailing our metrics and our goals. Ultimately we want to have a speed inde…

  22. comment
    Comment #22877510

    GitLab community advocate here! I wanted to let everyone know about a challenge we're holding right now. If you send us your review of GitLab vs GitHub (whether positive/negative/n…

  23. comment
    Comment #21398856

    Hi GitLab employee, we used the same mailing list as the one we used for the first email, so that's why you still received it. If you deleted your account you won't get any future …

  24. comment
    Comment #21360065

    (GitLab employee... of course) Sorry this thread kept you up (no sarcasm). If it helps at all, I'm responding to you right now because I'm here gathering all of the feedback, since…

  25. comment
    Comment #21355908

    Thank you for this! We've been creating a point-by-point list like this as well but your point #2 especially is something I don't think we've included, I'll add it.