Dmitri Shuralyov

@bradfitz Is this project (as well as [`issuemirror`](https://godoc.org/github.com/bradfitz/issuemirror)) still needed? Or is it better to remove or deprecate it, given we have `x/build/maintner` and `x/build/maintner/godata` now, which as far as...

> I would LOVE servegoissues on top of maintner. > > And I would gladly delete these repos then. Awesome! Glad to hear that. > I'm sure I have servegoissues...

Maybe you misread when I said this: > (if you would like to have it around) I meant... "if you think `servegoissues` is worth having and find it useful". Which...

I'm working on the new `servegoissues` on top of [`*maintner.GitHub`](https://godoc.org/golang.org/x/build/maintner#GitHub) API now. @bradfitz, in 2016, you said: > I'd like to start mirroring a number of github project's issues so...

I think I'll go with the http://localhost:8080/golang/go/123 scheme anyway, just so the code is general and works with any `*maintner.Corpus`.

What font would you like the new `servegoissues` to use? I was going to just go with `sans-serif` and such, but now tempted to use the Go font. It looks...

Ok, I'm done with the initial prototype. It's at a point where most things work, and whatever minor things are left (e.g., adding support for additional event types, colors for...

Here are some screenshots of what it looks like right now. /cc @bradfitz @rakyll   

> Want to put it under golang.org/x/build/maintner for now? Somebody wanted to move maintner away to its own repo, which we might do later, but we'd do it while preserving...

> Go font is fine if you care. We'll be the main users, and it makes us happy, so sure. Great! One last thing/question. I've decided to place the implementation...