Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
spec:issues [2014/07/21 11:24] – [3. Address (and communicate!) your Issues] fantasaispec:issues [2014/07/21 11:39] – [Best Practices for Issue Resolution] fantasai
Line 1: Line 1:
 ====== Best Practices for Issue Resolution ====== ====== Best Practices for Issue Resolution ======
  
-So you're a spec editor now. Congrats! You my think you will be spending your days drafting beautifully-crafted spec text to describe the newest features you've just dreamed up, but in fact, you will //mostly // be living in a mailing list addressing all the bugs in what you (or your predecessor) have already written.+So you're a spec editor now. Congrats! You may think you will be spending your days drafting beautifully-crafted spec text to describe the newest features you've just dreamed up, but in fact, you will //mostly // be living in a mailing list addressing all the bugs in what you (or your predecessor) have already written.
  
 Fear not! There is a (temporary) end to the issues (if you are diligent enough to hit Inbox Zero). Note: This is sometimes called Last Call. It will flood you with more issues. Fear not! There is a (temporary) end to the issues (if you are diligent enough to hit Inbox Zero). Note: This is sometimes called Last Call. It will flood you with more issues.
Line 45: Line 45:
   * [[http://wiki.csswg.org/spec#coordination-between-specifications|CSS Cross-module Coordination]], tips for cross-spec consistency   * [[http://wiki.csswg.org/spec#coordination-between-specifications|CSS Cross-module Coordination]], tips for cross-spec consistency
  
-But another part of it is also communicating the issue and its resolution to the community, including the commenter, affected implementers, and the CSSWG community.+But another part of it is also creating a resolution that represents the common understanding (or consensus) of the CSS community, including various commenters, affected implementers, and the CSSWG. To do that you have to not only solicit and incorporate feedback, and but also communicate outwards the results.
  
 ==== Choose Your Authority ==== ==== Choose Your Authority ====
Line 78: Line 78:
 ==== Raising Issues to the WG ==== ==== Raising Issues to the WG ====
  
-Sometimes its appropriate to raise an issue to the WG discussion. You can look at the CSSWG as a bureacratic approval committee that you must appease. Or, you can look at it as a group of really smart and knowledgeable people who care about making your spec better but whose attention you need to cultivate because we're all way too overloaded to read every thread on www-style. Personally, I start with the assumption that the CSSWG’s review would be very useful on everything, but attention is a limited resource so my job is to+You can look at the CSSWG as a bureacratic approval committee that you must appease. Or, you can look at it as a group of really smart and knowledgeable people who care about making your spec better but whose attention you need to cultivate because we're all way too overloaded to read every thread on www-style. Personally, I start with the assumption that the CSSWG’s review would be very useful on everything, but attention is a limited resource so my job is to
   - Filter out issues they don't need to care about because they're trivial.   - Filter out issues they don't need to care about because they're trivial.
   - Do a really good job of summarizing the issue so as many people as possible can really understand the problem and the proposed solutions (if any) and help resolve the issue better than I could by myself.   - Do a really good job of summarizing the issue so as many people as possible can really understand the problem and the proposed solutions (if any) and help resolve the issue better than I could by myself.
 
spec/issues.txt · Last modified: 2014/12/09 15:48 by 127.0.0.1
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki