Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't reference GitHub in the client? #11038

Open
nadonomy opened this issue Oct 3, 2019 · 2 comments
Open

Don't reference GitHub in the client? #11038

nadonomy opened this issue Oct 3, 2019 · 2 comments
Labels
A-Feedback-Reporting Reporting process for bugs, debug logs (rageshakes), suggestions O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement X-Needs-Product More input needed from the Product team

Comments

@nadonomy
Copy link
Contributor

nadonomy commented Oct 3, 2019

We suggest to users throughout the app to file/report issues in GitHub, which is fine for devs, but not really anyone else.

While we're shipping Riot as a 'reference client' it's fine, but for actual end-users it's bewildering.

We should discuss internally how to solve this, including entertaining more user friendly solutions like Uservoice, and figure out how to move forward from there.

Ideally we'd host some pages/a service on *.riot.im where riot users can view/submit issues there. I wonder if there's an easy way for us to expose our GitHub issues there without having to expose non technical users to GitHub itself? Or if we could expose this in the client better somehow?

@turt2live
Copy link
Member

One option is improving our rageshake system and (maybe?) expanding it to open issues on behalf of people. This would lead to us just having a giant text box with some prose to encourage people to leave symptoms and reproduction steps in the field. There could also be a "I'm making a suggestion" button instead to sort those out of bugs.

@nadonomy
Copy link
Contributor Author

nadonomy commented Oct 3, 2019

That would be great actually. I'm also now wondering how Riot should bias between reporting issues to us (as Riot devs) vs Riot admins.

@jryans jryans added T-Enhancement A-Feedback-Reporting Reporting process for bugs, debug logs (rageshakes), suggestions labels Oct 7, 2019
@kittykat kittykat added S-Minor Impairs non-critical functionality or suitable workarounds exist X-Needs-Product More input needed from the Product team O-Occasional Affects or can be seen by some users regularly or most users rarely labels Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Feedback-Reporting Reporting process for bugs, debug logs (rageshakes), suggestions O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement X-Needs-Product More input needed from the Product team
Projects
None yet
Development

No branches or pull requests

4 participants