Re:Things I would build if I worked at GitHub
by zeckalpha on Wednesday August 05, 2015 @11:18PM
(#10014360)
So that's the one blocker? Creating an issue via email?
[ Parent
| on HN ]
Re:Things I would build if I worked at GitHub
by scrollaway on Wednesday August 05, 2015 @11:21PM
(#10014369)
No, the blocker is setting up mailing lists with a forum-like interface (cf. discourse), but integrated to github (uses the github account) and without actually having to do the setup. Also, without polluting issues.
Re:Things I would build if I worked at GitHub
by e12e on Wednesday August 05, 2015 @11:32PM
(#10014387)
Actually opening issues via email would be nice to. Trac isn't perfect, but I remember email2trac[1] quite fondly. Combined with email notifications on change, it made it easy to forward bug/error-reports to a trac instance, and automatically create an issue. Or just let support@ go straight to trac.
I still think having an email interface (as in: in addition to a REST API) is very useful. Having a web interface as well isn't bad either.
Re:Things I would build if I worked at GitHub
by dvanduzer on Thursday August 06, 2015 @01:35AM
(#10014729)
Good project-specific labels to GH issues solves the "polluting" problem. The label/tag system is nicely flexible.
It sounds like what you really want is nested threads and top quoting and/or interstitial quote/response features?
(Arguably what you really need is commonly called a conference.)