W3C home > Mailing lists > Public > public-tracking@w3.org > September 2011

[proposal] Template for communicating our issues

From: Karl Dubost <karld@opera.com>
Date: Sat, 17 Sep 2011 18:37:58 -0400
Message-Id: <2B9364FA-6D22-459A-9701-94C7841B46FA@opera.com>
To: public-tracking@w3.org
Hi everyone,

to avoid losing too much time in collecting use cases and to ground our discussions in pragmatic cases meant to solve current issues, I propose to write our issues according to:

# Summary 
  What is the issue?
  (1 simple short sentence)

# Issue 
  What problem are we trying to solve (one issue only)
  (1 or 2 paragraphs)

# Positive Effects
  Why should we care? What are we improving for people? implementers?
  (1 or 2 paragraphs)

# Risks
  Are there any risks associated with this feature, proposal?
  What might fail and why?

# Implementations
  Is it already implemented?
  Where? How? Who?

# Related
  List of references
  (specification, tutorial, articles, code)

ps: mostly stolen from the W3C HTML WG and the (now defunct) W3C QA WG

Karl Dubost - http://dev.opera.com/
Developer Relations & Tools, Opera Software
Received on Saturday, 17 September 2011 22:38:44 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 21:44:40 UTC