+1, we'll hit some rough spots in the coming months, but the end result will be achieved. Thanks for the input.
-----Original Message----- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Wednesday, February 10, 2016 4:21 PM To: Mangefeste, Tony <tony.mangefe...@intel.com>; Laszlo Ersek <ler...@redhat.com> Cc: edk2-devel@lists.01.org <edk2-de...@ml01.01.org> Subject: Re: [edk2] Task: Issue Tracking System for Tianocore On 2/10/16 3:59 PM, Mangefeste, Tony wrote: > I've gone down the track of using Bugzilla as well. Aside from the massive > list of pros listed below, gathering any other preference is welcomed. I > have used Bugzilla, but never been a maintainer on it. We do have some > resources lined up for management of Bugzilla, if needed, so that's not a > barrier. Of course, the devil's in the details. > > So in short, Bugzilla is top of my mind right now. I'm looking at other OSS > projects and seeing what they use. If anyone here sees one not listed below > or has an opinion that they care to express please do so. On the mobility > view, I'll try to play around with that and see how it looks on my mobile > devices. I'm currently hosting a mirror of the edk2 repo at https://edk2.bluestop.org/diffusion/EDK/ - Phabricator has a bug/task tracker module Maniphest that looks rather capable - https://phacility.com/phabricator/maniphest/ . I just think it's a shame we've lost so many bugs by telling people to report them to the mailing list for a couple of years, so any issue tracker is good at this point! -- Bruce _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
