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

Error Reporting Page #97

Open
TBye101 opened this issue Dec 2, 2018 · 3 comments
Open

Error Reporting Page #97

TBye101 opened this issue Dec 2, 2018 · 3 comments

Comments

@TBye101
Copy link
Owner

TBye101 commented Dec 2, 2018

An error reporting page accessible from the main menu would be nice. Possibly use OctoKit to enable users to submit errors directly to the GitHub page? Or maybe a layer inbetween would be nice so that user junk (Things that aren't errors) don't get to the GitHub page.

@TBye101 TBye101 added this to To do in Features via automation Dec 2, 2018
@a2937
Copy link
Contributor

a2937 commented Apr 23, 2019

I thought about your idea and have a different idea about what you can possibly do. What if it instead had a form and used MailKit on the Client GUI portion have the ability to send feedback with optional fields for name and email address. As long as handling possible trolls is something you can manage; then everything should be fine.

@a2937
Copy link
Contributor

a2937 commented Apr 23, 2019

Both ways might possibly require passwords however.

@TBye101
Copy link
Owner Author

TBye101 commented Apr 23, 2019

Personally I like the first option better. I'll explain why:

By using Octokit we can put user errors/exceptions directly into the GitHub repository. This gives visibility of the issues to everyone who works on this project. If we were to use some sort of email solution, only people who have access to the email account could see these. Furthermore that would also require people to check a separate location for errors.

Security isn't critical for the Octokit route as some clever use of authentication services like OAuth as well as a new separate GitHub account for this purpose with limited permissions would leave things fairly secure. I guess the same could be said for the email route, but I favor the increased visibility and convenience of having the issues directly within this repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Features
  
To do
Development

No branches or pull requests

2 participants