Miscellaneous improvements to CONTRIBUTING.md

Author: fantasai

CONTRIBUTING.md

@@ -14,7 +14,7 @@ in the relevant W3C Working Group or make a non-member patent licensing commitme
 
 ## Issue disclosure and discussion
 
-The first step for any contribution, substantive or not, is to either:
+The first step for any substantive contribution is to either:
 
   1. [Find an existing issue](https://github.com/w3c/csswg-drafts/issues) directly related to the contribution
   2. [Add a new issue](https://github.com/w3c/csswg-drafts/issues/new)
@@ -24,29 +24,40 @@ that the eventual consensus can be turned into official specification language.
 
 If you are familiar with a [GitHub-based pull request contribution workflow](https://help.github.com/articles/about-pull-requests/), 
 please note that **most issues are subject to quite a bit of discussion** before 
-draft language becomes ready for a pull request. Please ensure the full problem 
-space of the issue is explored in the discussion, and that consensus has been reached 
-by the participating members, before contributing to the 
-repository.
+they are ready for a pull request with specific wording changes. Please ensure
+the full problem space of the issue is explored in the discussion, and that
+consensus has been reached by the participants, before drafting a pull request.
 
 ## Normative and/or substantive contributions
 
 The CSS Working Group operates via the consensus of its membership, and discusses 
 all significant matters prior to implementation.
 
-If adding an new, normative issue, please label/tag the PR as 'Agenda+' to bring 
-it to the Working Group's attention.
+The Editors responsible for a particular spec are responsible for triaging their
+issues on a regular basis; however note that sometimes this can take awhile
+(anywhere from a few days to a few years) depending on the complexity of the
+issue and the work schedules of people involved--this does not mean we are
+ignoring the issue.
 
-The Working Group, aside from managing issues on GitHub, mainly discusses specifications 
-and requests on [the www-style public mailing list](https://lists.w3.org/Archives/Public/www-style/), 
-and in CSSWG meetings.
+For an issue that requires WG discussion or approval, WG members can tag/label
+it 'Agenda+' to bring it to the Working Group's attention. Unfortunately,
+GitHub doesn't allow labelling permissions without repository write permissions,
+so if you believe an issue is urgent or discussion has stalled for awhile and
+the WG's attention is needed to move forward, ask one of the editors to flag it.
+
+The Working Group, aside from managing issues on GitHub, mainly discusses
+specifications and requests on [the www-style public mailing list](https://lists.w3.org/Archives/Public/www-style/),
+and in CSSWG meetings, whose minutes are posted to www-style.
 
 ### After discussion
 
-Once the Working Group has come to a consensus, a contributor may file a pull request 
-against the issue. The editor of the specification related to the issue will then be 
-responsible for reviewing both the content and implementation of the contributed 
-changes.
+Once the Working Group has come to a consensus, the editor may draft up and
+commit the relevant changes for review by other contributors or a contributor
+may file a pull request against the issue for review by the editor(s). Since
+specification wording is tricky, it is strongly recommended that the editors
+of that particular spec be involved, either as originator or as reviewer, in
+any changes. We also encourage other participants in the issue discussion to
+review the changes and request corrections or improvements as necessary.
 
 Please follow the [Pull Request template](https://github.com/w3c/csswg-drafts/blob/master/.github/PULL_REQUEST_TEMPLATE.md) 
 when contributing to the repository.
@@ -70,6 +81,11 @@ The pre-CR specifications with this testing requirement are currently:
 
 ## Non-substantive contributions
 
-For simple spelling, grammar, or markup fixes unrelated to the substance of a specification, 
-please file an issue with the usual shortname tagging (ie. `[css-foo]`) for the spec(s) 
-edited by the change. You may then issue a pull request referencing the issue number.
+For simple spelling, grammar, or markup fixes unrelated to the substance of a
+specification, issuing a pull request without a corresponding issue is acceptable.
+
+## Further information
+
+See [about:csswg](http://fantasai.inkedblade.net/weblog/2011/inside-csswg/)
+for more information on how the CSSWG operates, delegates authority, and
+makes decisions. Someday maybe we'll also have a useful official website.