2015-09-25 9:57 GMT+02:00 Torsten Zuehlsdorff <mailingli...@toco-domains.de>: > > > On 24.09.2015 20:23, David Fetter wrote: >> >> On Thu, Sep 24, 2015 at 12:10:07PM -0600, Ryan Pedela wrote: >>> >>> Kam Lasater wrote: >>>> >>>> I'd suggest: Github Issues, Pivotal Tracker or Redmine (probably in >>>> that order). There are tens to hundreds of other great ones out there, >>>> I'm sure one of them would also work. >>> >>> >>> Why not just use Github issues? >> >> >> Is Github issues something we can run ourselves? >> >> If not, it's a proprietary system which has a proprietor whose >> existence even next month is not guaranteed, and whose interests are >> not guaranteed to align with ours into an indefinite future. >> >> In some very important sense, it does not matter what features a >> system has if it isn't one we can control. At a minimum, this means >> we need to run it in its entirety on resources we control, and we need >> to be able to patch any piece of it on our own say-so. > > > + 1 > > Instead of Github maybe GitLab is a good choice. There is an open source > community edition you have the full control over. And it is used by more > than 100.000 organizations: > > https://en.wikipedia.org/wiki/GitLab >
Of course everyone has their own preferences. Just wanted to point you to roundup [1]. It's: - Simple - Python - Very easy to extend - Integrates well with e-mail - Complete web interface We use it for the Tryton [2] project and the source code we use is available here [3] so you can take a look how easy it is to add new fields and other stuff. We use mercurial but commits automatically close the bug reports and we have links with the codereview. [1] http://roundup.sourceforge.net/docs/features.html [2] https://bugs.tryton.org [3] http://hg.tryton.org/bugs.tryton.org/ -- Albert Cervera i Areny Tel. 93 553 18 03 @albertnan www.NaN-tic.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers