Hacker Newsnew | past | comments | ask | show | jobs | submit | emilycook's commentslogin

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/


Wow, awesome! Thanks Emily!


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


Does Mattermost also have "uncollapsed" threads like Flowdock? Personally, I think hiding conversation in a group channel is terrible UX. I don't know why people are aping Slack's functionality when I hear almost universally that it sucks.


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.


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


That's not a similar policy.


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


What's an "active project"? OP says they discovered that their account had been renamed by having their workflow break. What kind of activity was OP regularly engaging in that depended on OP's account existing with the original name but did not flag OP's account as active?


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/


Hi Emily, can you guys do an upper limit, say maximum 1.5 seconds load time for any page? Ruthelessly disapprove features unless it meets this spec time.

When a website or service becomes too slow, it is on its way to an impending death. Then people wonder why some service fell apart? Put users and usability first and foremost before features.


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


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: