Skip to content

WICG Best Practices

Jump to bottom Edit New page
Stuart P. Bentley edited this page Jul 27, 2015 · 1 revision

  1. Speak up. The whole point of the WICG is that there's pretty much no barrier to entry: if you're not familiar with all the discussion and/or technical details surrounding a certain topic, but the overall concept appeals to you, tell us about it. Best case scenario, people will explain these things to you: worst case scenario, it'll be a little more noise to skim over.

    (Caveat: if you're going to speak up, do so in a detailed fashion - explain your thoughts, at the minumum explaining what it is about the issue that matters to you. The whole point of speaking up is to suggest something for new discussion to incorporate and address. The only thing comments like "+1!" suggest for discussion is posts complaining about people posting "+1" comments, and then an infinitely spiraling series of posts complaining about the complaints, like a shush in a movie theater or a "reply all" to a mailing list that spreads like wildfire.)

  2. Participate in as many places as you can. I personally jump between here and GitHub: others participate here and in the mailing lists, or on the mailing lists and on GitHub. (I've participated in the mailing lists every now and then - I'd probably participate in the mailing lists more if I had a decent web client for posting to them, instead of having to spin up Thunderbird and point it at GMANE.)

  3. Summarize discussions. Explain the conclusions other efforts have come to: what problems rose, what actions were taken, what would need to happen to move forward. This is what half of Tab Atkins' posts here are dedicated to, and it does a fantastic job of focusing/directing the thread toward something that can actually happen.

  4. Suggest actions. Think about what would be involved in making a discussion a reality.

  5. Hyperlink everything. The cost of somebody seeing a link that maybe isn't relevant to them (they have to take two seconds to figure that out) is way lower than the cost of somebody not seeing a link that would have been relevant to them (they spend several hours / weeks / months incompletely duplicating someone else's effort), so drop in links with wild abandon. (What would be awesome would be if we could start including these cross-discussion links as part of the spec documents, but that's putting the cart before the horse right now.)

Originally from http://discourse.wicg.io/t/wicg-best-practices/942

Add a custom footer
Add a custom sidebar
Clone this wiki locally