> I agree that a bug tracker can help. It may be hosted outside W3C > servers, so it would be a significant contribution if someone accepts to > host it. Is there any reason for not using the existing W3C bug tracker, previously suggested [1]? Apart from being used to track specifications ("SVG" product [2], for example), it is already being used by software products as well ("CSSValidator" product [2], for example). Reusing an existent framework would be, IMHO, better for: maintenance reasons (someone already has the responsibility to maintain the W3C bug tracker); familiarity (the bug tracker is already used for other W3C activities so it should be familiar to most users; also, it is bugzilla-based, one of the most widely deployed bug trackers); probably some more reasons I could try to gather, if needed. Sorry if this sounds as noise: I'm trying to suggest a quick and hassle-free setup which may also (potentially) help avoiding additional work in the future (while comparing to a project-specific bug tracker). :-) Hope this helps, Helder Magalhães [1] http://lists.w3.org/Archives/Public/www-amaya/2008JulSep/0035.html [2] http://www.w3.org/Bugs/Public/query.cgiReceived on Thursday, 21 August 2008 10:30:21 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:30:56 UTC