emilycook

6 ms·

1.
by emilycook 5y ago
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 community server http://community.mattermost.
2.
by emilycook 5y ago
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 according to your preferences.
3.
by emilycook 5y ago
I work at Mattermost -- we do have this, it's just still in beta right now https://docs.mattermost.com/messaging/organizing-conversatio...
4.
Mattermost End-to-End Test Automation Hackathon: May 3 – May 31(mattermost.com)
4 points by emilycook 5y ago|1 comments
5.
by emilycook 5y ago
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 manual tests Our end-to-end (E2E) tests, written in JavaScri
6.
by emilycook 5y ago
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: https://community.mattermost.com/ and lo
7.
by emilycook 6y ago
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://news.ycombinator.com/item?id=23827772
8.
by emilycook 6y ago
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://docs.github.com/e
9.
by emilycook 6y ago
For future reference, you can see what we consider dormant here: https://about.gitlab.com/support/#dormant-namespace-requests
10.
by emilycook 6y ago
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 actual users. Although I do want to point out that GitH
11.
by emilycook 6y ago
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/performance/
12.
by emilycook 6y ago
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.
by emilycook 6y ago
oops misspoke and now I can't edit, I meant deployment of applications to AWS (hopefully you knew what I meant!)
14.
by emilycook 6y ago
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] -simplified deployment of GitLab to Amazon ECS [2] -added ep
15.
by emilycook 6y ago
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.
by emilycook 6y ago
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 passed along the feedback to our product team!
17.
by emilycook 6y ago
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 an issue we're working on. Here is our handbook p
18.
by emilycook 6y ago
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 hopefully it'll be more intuitive soon! [1] https:/&
19.
by emilycook 6y ago
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.
by emilycook 6y ago
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 accountability metric, more of an estim
21.
by emilycook 6y ago
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 index of less than 2 seconds for .com, but we know we aren'
22.
by emilycook 6y ago
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/neutral), we'll send you some swag. We kn
23.
by emilycook 7y ago
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 emails.
24.
by emilycook 7y ago
(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 there was so much discussion on here/reddit&
25.
by emilycook 7y ago
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.
26.
by emilycook 7y ago
Sorry for being unclear I wasn't trying to refute the accuracy of the title, only to provide additional context that was missed by us in the first place. I think if anything it's really not my place to have a say in what the tit
27.
by emilycook 7y ago
(GitLab employee) we're discussing other options too, I'm personally advocating strongly against just going ahead with the current plan. My preference would be for no third-party involvement and just better ways to analyze the dat
28.
by emilycook 7y ago
It is the feedback from you all that is responsible for us rolling back the ToS and reconsidering our approach to this. My job, genuinely, is to relay concerns back to the people who make decisions like this. Sid has said in another comment
29.
by emilycook 7y ago
I realize this is also spammy, my bad, but I do wanna clarify that it's explicitly our job to respond to questions/concerns and relay feedback to the company: https://about.gitlab.com/handbook/marketing/c
30.
by emilycook 7y ago
The ToS have been rolled back, and telemetry had not been implemented yet. I (of course) don't want anyone to leave, but hopefully that alleviates any concerns if people want to.

More ›