docsprint to update documentation

[marcoscaceres]

We should try to organize a doc sprint (e.g., 1 hour), where a group of us get together (virtually) and update the documentation. If we get 3-5 of us together, each take a chapter, we could get it done quick.

[darobin]

I was thinking of using my geek week (W3C folks get one week where all they do is geek out on absolutely whatever, as opposed to the rest of the year when we geek out on just more or less whatever) for this, but if there are volunteers to help I'm more than happy to do this in sprints — you can count me in.

I reckon that a first pass might actually be more about reorganising the docs (what we already have, how to split the docs into smaller, clearer bits) than writing. WDYT?

[marcoscaceres]

yeah, that makes sense - it would be good to think about how people approach the document to get just the bits they need. Be good to also centralize the documentation in the repo instead of at:
http://dev.w3.org/2009/dap/ReSpec.js/documentation.html

[darobin]

Yeah, I need to pull CVS out of my arse to make the above redirect to the version on GitHub.

Do you want to get a discussion about this rolling on spec-prod? I think we'll find volunteers.

[marcoscaceres]

Sure! It might also be a fun thing to do at TPAC, if we can't do it earlier. Be nice to meet and chat with other Respec'ters and compare scars :)

[darobin]

We could, but I'd like to get the docs sorted earlier than that. Also, TPAC is usually very busy :) But a breakout session on ReSpec might be good indeed.

[darobin]

This has been taken care of, see https://github.com/darobin/respec-docs/ to contribute.