Update the "Send a bug report" window to use GitHub #114
Comments
I think we could make a "DrRacket User" account on GitHub, and Dr.Racket could store whatever auth keys GitHub requires. |
|
Wouldn't this have a high risk of being hijacked and the account misused? I'd say disclosing the account's OAuth token or other API key would be unwise, unless GitHub's permission system is fine-grained enough to get a token which only allows submitting bugs for a small set of repositories. We could however have a minimal server which just accepts a title and body string, and posts it as an issue on one of the allowed repos on the user's behalf. The difference is that keys would be stored on the server and not disclosed. I'm just making guesses here, though. |
|
I think that something inside DrRacket that directs someone to a relevant github page (and maybe a FAQ page about issues that we make on our wiki?) is sufficient. |
|
GitHub's issue templates can also be used if we want to make sure some information is filled in by the template (like is done for the TR repo). Although @samth said (racket/racket#1695 (comment)) that there is something in the works. |
|
On Wed, May 17, 2017, 7:32 PM Georges Dupéron ***@***.***> wrote:
Wouldn't this have a high risk of being hijacked and the account misused?
Yes.
I'd say disclosing the account's OAuth token or other API key would be
unwise, unless GitHub's permission system is fine-grained enough to get a
token which only allows submitting bugs for a small set of repositories.
This isn't possible, and embedding the key is not allowed by GitHub's
policies.
We could however have a minimal server which just accepts a title and body
string, and posts it as an issue on one of the allowed repos on the user's
behalf. The difference is that keys would be stored on the server and not
disclosed. I'm just making guesses here, though.
We could do that, but I don't want to run a server for just that.
… —
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#114 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAO78x_CpPzLOcFV0NkFOa0e4lPT2r7Kks5r64OSgaJpZM4NeMxx>
.
|
How many people using the submit a bug tool actually have github accounts though? And creating one may be a large barrier to entry for new users to submit a bug. |
|
Yes, I agree this a concern. When compared with the alternatives, however, I think it is the best option we have. The wiki page could also suggest posting on our mailing list, which has a lower barrier to entry, and helpful people who would, I expect, either submit issues or explain how to. |
|
Fair concern. What about using something like this?: https://gitreports.com/ Then we can have github issues without managing our own server or requiring users to log in. |
|
@LeifAndersen https://gitreports.com/ looks like a great solution. Two minor itches:
|
|
Regarding your first point...ugg...I didn't notice the captcha. I'll file a bug report with that repo, they realliy should have a low vision option. |
|
Hi, I believe the current situation is worse than users having to create a GitHub account. While a perfect solution is being developed, I have created an interim solution using the default 'submit bug report' template. This required two actions As there are already existing examples of this I believe (b) could be a I note that the title is passed as a parameter - this is worth investigating to see if some environment details can be passed this way, as per the old bug report mechanism. Kind regards, Stephen Current situation if user attempts to us the submit bug via the help screen; User fills in form, presses submit, after a long wait the following error is returned;
|
The "Send a bug report" window uses http://bugs.racket-lang.org/, which seems to be the old bug tracker (and GitHub is preferred nowadays).
The submit code should be updated to use GitHub instead.
It would be possible to either open
https://github.com/racket/REPO/issues/new?title=foo&body=barin the user's browser, or use the GitHub API to directly submit the bug (this would however likely require that the user has a GitHub account).The text was updated successfully, but these errors were encountered: