# Bug tracker (again) 2 messages from 2014-02-08 to 2014-02-08. Participants: Duy Nguyen, brian m. carlson. Thread: https://gitlist.dev/t/35829 ## Duy Nguyen, 2014-02-08 07:26 Subject: Bug tracker (again) Message-ID: URL: https://gitlist.dev/e/CACsJy8BvEhqBSv2nGG3PTC3aarURAMic0SwMVppeDRkSXiZfCQ%40mail.gmail.com ``` (Dropped some CC as this becomes a different topic) On Sat, Feb 8, 2014 at 2:20 AM, Jonathan Nieder wrote: > Duy Nguyen wrote: > >> Don't take it the wrong way. I was just summarizing the last round. It >> surprised me though that this went under my radar. Perhaps a bug >> tracker is not a bad idea after all (if Jeff went missing, this bug >> could fall under the crack) > > I'm happy to plug > - http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=git;include=tags:upstream > - http://packages.qa.debian.org/common/index.html (email subscription link: > source package = git; under "Advanced" it's possible to subscribe to > bug-tracking system emails and skip e.g. the automated build stuff) > - https://www.debian.org/Bugs/Reporting (bug reporting interface - > unfortunately the important part is buried under "Sending the bug > report via e-mail") > again. :) So I wonder if we use debian bug tracker for git upstream. I haven't used debian tracker much (or debian for that matter). It's probably best just ask instead of searching and guessing. I suppose if debian people (mostly debian git maintainer?) are not opposed to us using their tracker for upstream bugs, then it's just a matter of associating a mail thread with a bug number for tracking. That could be probably be done via email, then reply all to the thread in question with a bug email address. After that all email discussions are also tracked via this bug email. Anybody can help track bugs. Say if 3 weekdays are over and nobody said a thing about something that looks a lot like bug, then it should be tracked (problems that can be quickly fixed do not need tracking). Hmm? -- Duy ``` ## brian m. carlson, 2014-02-08 18:18 Subject: Re: Bug tracker (again) Message-ID: <20140208181825.GL635004@vauxhall.crustytoothpaste.net> URL: https://gitlist.dev/e/20140208181825.GL635004%40vauxhall.crustytoothpaste.net In-Reply-To: ``` On Sat, Feb 08, 2014 at 02:26:57PM +0700, Duy Nguyen wrote: > So I wonder if we use debian bug tracker for git upstream. I haven't > used debian tracker much (or debian for that matter). It's probably > best just ask instead of searching and guessing. > > I suppose if debian people (mostly debian git maintainer?) are not > opposed to us using their tracker for upstream bugs, then it's just a > matter of associating a mail thread with a bug number for tracking. > That could be probably be done via email, then reply all to the thread > in question with a bug email address. After that all email discussions > are also tracked via this bug email. Anybody can help track bugs. Say > if 3 weekdays are over and nobody said a thing about something that > looks a lot like bug, then it should be tracked (problems that can be > quickly fixed do not need tracking). Hmm? All interaction with the Debian BTS (except for viewing bugs) is done over email. That's what I like about it. It will automatically insert an appropriate piece in the subject line (Bug#1393:) and anyone can mail the control bot to manipulate a bug. It also has the concept of usertags, so you can create your own set of tags with user git@vger.kernel.org (or your personal address, if you desire), and then sort and display bugs appropriately. Junio seemed lukewarm on the idea of using a bug tracker; however, I think debbugs (either the Debian BTS or a separate instance) is probably the best-suited to an email-based workflow of all the systems I've used. Of course, it's up to the regulars (and probably ultimately Junio) whether this is something that Git as a project would benefit from. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 ```