emilycook

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.com/

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.

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

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 JavaScript using the Cypress framework, help us cut down manual tests, and are an integral part of the product development process.

Event Details

1. Event runs from May 3rd to May 31st, 2021. Any submitted PRs must be merged by June 11th 4:00 PM PST to qualify. Those closed by maintainers as incomplete, invalid or spam are not counted.

2. Five merged pull requests wins you a swag bag

3. Top-3 contributors win a special award.

4. First-time contributors receive a custom-printed Mattermost Mug! https://forum.mattermost.org/t/limited-edition-mattermost-mu...

How to Join

1. Join our Test Automation Hackfest channel in Mattermost: https://community.mattermost.com/core/channels/e2e-test-auto...

2. Review test cases ready for automation: https://docs.google.com/spreadsheets/d/1auZlKnfWPtAXhl0dJYyN...)

3. Find a test case you’re interested in and either post in the Test Automation Hackfest channel, or comment in the spreadsheet.

4. Create a pull request to add a Cypress test automation using this guide: https://developers.mattermost.com/contribute/webapp/end-to-e...

Resources

* Announcement blog post: https://mattermost.com/blog/mattermost-e2e-cypress-test-auto...

* Automated UI testing with Cypress: https://mattermost.com/blog/automated-ui-testing-with-cypres...

* E2E Testing in Mattermost documentation: https://developers.mattermost.com/contribute/webapp/end-to-e...

* Spreadsheet of test cases to automate: https://docs.google.com/spreadsheets/d/1auZlKnfWPtAXhl0dJYyN...

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 look at our developer docs: https://docs.mattermost.com/guides/developer.html

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

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/en/github/site-policy/github-usernam...

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

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 GitHub also has this [2], it's just worded differently and doesn't outline what they consider "inactive".

[1] https://about.gitlab.com/support/#dormant-namespace-requests

[2] https://docs.github.com/en/github/site-policy/github-usernam...

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/

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

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

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 epic hierarchy on roadmaps (+ other improvements to our epic and milestone features) [3]

[1] https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-rel...

[2] https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-rel...

[3] https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-rel...

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.

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!

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 page that outlines our current metrics and goals, our primary goal is to have a speed index of less than 2 seconds per each page on .com: https://about.gitlab.com/handbook/engineering/performance/

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://gitlab.com/gitlab-org/gitlab/-/issues/30933

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.

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 estimate that can change dynamically when new problems arise so we can roughly plan out when a feature is going to be released. Granted we don't have a boss who would beat us over the head with that. Thank you for the feedback though I'll make sure to pass it along.

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't quite there yet.

As for the UI being unintuitive, I'm sorry to hear that. Everyone has different UI preferences so it's understandable. If you want, we're holding a competition right now [2] for anyone who writes a review of GitLab vs GitHub if there are any specific features within GitHub's UI that you like better!

[1] https://about.gitlab.com/handbook/engineering/performance/

[2] https://about.gitlab.com/blog/2020/04/14/github-free-for-tea...

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 know competition is good for end-users, so now it's our turn to evaluate what we're doing right and what we can improve upon.

https://about.gitlab.com/blog/2020/04/14/github-free-for-tea...

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.

(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/twitter/the issues that need consolidating. I'll be making a lot of noise so the people in charge can truly see the impact this had

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.

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 title says.

(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 data we already have

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 that he wasn't expecting praise, but didn't expect the backlash to be this bad. If they were I really wish they would've given me a heads-up

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/community-relati...

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.

We have been taking the feedback seriously, we rolled back our ToS changes and are reconsidering our approach here. More info can be found on the issue