The front end could also use some kind of matching algorithm to find
potential pre-existing bugs.

On 13 July 2015 at 11:23, Brad Fitzpatrick notifications@github.com wrote:

@adg https://github.com/adg and I were discussing putting a little web
app up in front of Github's actual issue tracker, to get better bug reports
from users.

The old code.google.com bug tracker let us present different types of
users (project owners/developers vs. users) different types of templates.
Github has nothing. As a result, we get some pretty incomplete bug reports.

Proposal:

• https://golang.org/issue/new and various other things would link or
  redirect to a new web app, e.g. https://bug.golang.org/
• https://bug.golang.org/ would take the user through an auth flow to
  get their Github auth token with permission to file a bug.
• https://bug.golang.org/ would then have users fill out a template
  form, asking the Go questions (version, OS/ARCH, go env, etc) which would
  help us debug.
• upon submit, we post a bug to Github as the original Github user.
  (Bugs aren't posted as a robot account)
• a bot would find bugs filed directly to Github without using the
  template and amend them with a hint to use the bug instead. Perhaps we even
  link to https://bug.golang.org/amend/NNNN where NNN is the incomplete
  bug report. We could then append to the bug with the details. The bot would
  not trigger for bugs filed by members of the project.

@adg https://github.com/adg also proposed baking some bug-filing
capabilities into the go command, but the details of that are fuzzy and
would be the subject of a separate bug. Let's not discuss that part here.

/cc @robpike https://github.com/robpike @rsc https://github.com/rsc

—
Reply to this email directly or view it on GitHub
#11695.

This sounds great. The front end could also guide users to ask questions on golang-nuts instead of filing issues. (The bot that finds bugs filed directly to GitHub should probably also provide that hint.)

This seems like an obviously good idea. Go for it. (Make sure the app only asks for public_repo.)

Is this something we still want? Since October, we got GitHub issue templates.

I think it could still be helpful.

I think it would still be a nice thing to have.

On 28 June 2016 at 08:36, Chris Broadfoot notifications@github.com wrote:

Is this something we still want? Since October, we got GitHub issue
templates.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#11695 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AIDilU-AhYtSyDH6MBjN3b5HRZChviW1ks5qQFBwgaJpZM4FXneO
.

If someone wants to tackle this, go ahead.

@adg Is this issue, and #16635 something we still want to pursue? I could work on this in October?

@andybons would be the person to talk to at this point.

It seems to me that the combination of github issue templates and go bug (new since the Jul 19, 2016 "go ahead" comment) greatly reduces the benefit of a whole separate web page. At this point the incremental benefit seems not clearly greater than the cost of implementation and ongoing maintenance. I'd even be OK with closing this issue at this point. Effort on tools might be better spent on others, like the PR gateway.

Leaving for @andybons

Is there a PR Gateway Issue I should review, and potentially work on, instead?

@SCKelemen the relevant issue for PR to Gerrit import is #18517. I’m working on an initial design document for that. Will update the bug with that once it’s in a good state.

@andybons is this ticket is going to be abandoned?

Not at the moment, no. There are questions I have about discoverability, though. How would we get people to actually use it? Can the current issues with bug reports be solved with more automation like gopherbot?

I’m also going to echo Russ’s comment about the incremental benefit. We have a lot on our plate so we can’t guarantee that the Go team at Google would take ownership should it be built.

If someone wants to start on a design for this, we are happy to consult, but I would outline the work to be done in this bug (or a google doc) before moving forward.

We built GerritBot to meet users where they were (GitHub PRs over Gerrit for CL creation). Building a tool to move them away from here for bugs seems like the opposite direction to take.

Please excuse my rambling. I think you get the gist of what I’m saying, though :)

Given that Github now has:

• templates, which we actively use (they weren't available in 2015 when this issue was created) https://github.com/golang/go/blob/master/.github/ISSUE_TEMPLATE
• auto complete suggesting similar issues based on lexicographic matches, as an issue is typed
• GerritBot to port Github PRs to CLs
• Gopherbot for automation and testing
• Github actions that are upcoming

perhaps let's revisit if we need to anything more here or rather leaving any remaining work to Github to implement.