Re: [tsc-devel] Self-hosting the project

Quintus | Sat, 12 Sep 2015 06:21:42 UTC

Hi xet7,

Gogs looks indeed nice. I played with the test instance at try.gogs.io,
and I’d be fine with using it for TSC.

As for the GitHub import issue stuff. GitHub’s API is fairly easy to
use, and it supports both issues and pull requests[1]. In fact, GitHub’s
API /will/ return pull requests as well when you request the issues
list, including a “pull_request” key in the JSON of each PR (normal
issues won’t have that one). I don’t know any Go, but if you can
programatically drive Gogs, importing should be a one-off script without
any need for external services. If not, one would probably have to
contribute the importer to Gogs itself. With lack of the Go language
that’s a bit difficult, though. Before making the final choice, we
should consider this hurdle.

Regarding the other topics you brought up in
<CABjjbE7stZQy+pe-xyyptODeae8-Caj_0AoYY=N-Ri63dHnY0A@mail.gmail.com>:

The missing wiki is not a problem. We can use separate wiki software
like Moinmoin. As I said in the OP, our choice doesn’t need to be
exclusive.

Hosting a translation service is also okay, as long as we also accept PO
files by people who do not use it.

Valete,
Quintus

[1]: https://developer.github.com/v3/issues/

Lauri Ojansivu <…x@x…> writes:

> Hi,
> I received reply from Gogs Google+ community:
>
> "Hi, it is not implemented yet, please see
> https://github.com/gogits/gogs/issues/809
> "
>
> So there we can see current progress.
>
> BR,
> xet7
>

-- 
#!/sbin/quintus
Blog: http://www.guelkerdev.de

GnuPG key: F1D8799FBCC8BC4F