SVG:Specification Issues: Difference between revisions

SVG:Specification Issues (view source)

13 bytes added , 21 June 2007

m

no edit summary

Confirmed users, Bureaucrats and Sysops emeriti

969

edits

@@ Line 8: / Line 8: @@
 * make sure the resolution is visible to all when an issue is closed
-Unfortunately, using a mailing list for issue reporting fails to provide even these most basic of requirements. This has resulted in countless hours wasted and much hair pulling and resentment on our part. While we may not be able to force the W3C to use a public issue tracking system, we can at least try to publicly track any new issues we find (and maybe even go back and dig up the old issues we've reported at some point). Hence this page.
+Unfortunately, using a mailing list for issue reporting fails to provide even these most basic of requirements. This has resulted in countless hours wasted and much hair pulling and resentment on our part. While we may not be able to force the W3C to use a reasonable, public, issue tracking system, we can at least try to publicly track any new issues we find (and maybe even go back and dig up the old issues we've reported at some point). Hence this page.
 Ideally issues should be tracked using issue tracking software, but that's often less accessible to "outsiders", and it can take time and many iterations to hash out a good clear description for an issue. In that respect, wiki pages (with their version history and the ability to revert changes) are very useful.
 * [[SVG:Specification_Issues:Embedding_by_Inclusion|Embedding by Inclusion]]