Whenever an issue/action is mentioned on the mailing list, a comment is added to the issue/action linking to the mailing list email.Tracker's interface is a lot less intimidating and ugly, and has far fewer form fields.Sends out email to reporters and others when issues are officially closed, change state, etc.However, the current Tracker system does offer several things that the WG would miss, as discussed below. Tracker is much less powerful than Bugzilla.A single system will avoid duplication, save us time, and encourage external people to use it instead of the list.There are several reasons to solely use Bugzilla, including: We should be getting them to use a robust, purpose built system, dammit! However, the unfortunate result is that external people are still using the "bad old system" of sending mail to the public list to report spec/test issues, where issues can be forgotten, unsatisfactorily resolved, intermingled with other issues, or spread across multiple separate threads. The reluctance of the WG to encourage use of Bugzilla is understandable since (besides Bugzilla's own shortcomings) having two separate issue tracking systems is a real pain. The WG currently uses the Tracker instance during its own day-to-day work, and so far has done little to encouraged external people to report issues directly to Bugzilla. We have a public Bugzilla instance where the public can report and comment on issues that the SVG WG needs to address, plus a semi-public Tracker instance that is writable only by members of the SVG WG. That leaves us with Bugzilla, and with figuring out how to make it meet our needs (and desires).Ĭurrently, issues that should be getting the attention of the SVG WG are tracked in two different places (three if you include the mailing list, but things tend to get lost/forgotten there). It is further assumed that Tracker does not meet the aims outlined above since jwatt's original proposal to allow the public to raise and comment on issues in the SVG WG's tracker was rejected because the W3C's System's Team don't believe home-spun solutions like Tracker get the required security attention to be safe enough to be opened up like that. This page assumes that Bugzilla and Tracker are the only issue tracking systems on the table, since it's been made clear that the W3C Systems Team is not going to support anything else due to resource constraints. To have the SVG WG use a single issue tracker where any interested party can at least view, open and comment on issues (this does not preclude having issues or fields on issue that can only be viewed/edited by members). 8 Making replies to bugzilla generated email appear as comments on the bug.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |