- From: Karl Dubost <karl@la-grange.net>
- Date: Thu, 23 May 2013 11:04:12 -0400
- To: Charles McCathie Nevile <chaals@yandex-team.ru>
- Cc: public-w3process <public-w3process@w3.org>, "Arthur Barstow" <art.barstow@nokia.com>
Le 23 mai 2013 à 09:56, Charles McCathie Nevile a écrit :
> Art Barstow:
>> I just scanned the Process Document's (PD) Table of Contents [ToC] and it seems like it could use some refactoring to enable more frequent updates and clarifications
[…]
> The Process basically documents some agreed obligations.
Checking what the Process Document says about itself:
The W3C Process Document describes the organizational
structure of the W3C and the processes related to the
responsibilities and functions they exercise to enable
W3C to accomplish its mission. This document does not
describe the internal workings of the Team or W3C's
public communication mechanisms.
— http://www.w3.org/2005/10/Process-20051014/
When I read "what to slash" in the mail subject, I was wondering what would be the best strategy for a new process document. Is it to "cut and distribute" in a way which makes the document still logical (cross-references difficulties) or is it to write it from scratch documenting what is done at W3C currently. Maybe it is longer to do. :/
Things I would like to see (not complete):
* What are the goals of the Process Document?
* What is the fundamental set of values governing the process?
* Roles
* Required steps for working (input/output/flowcharts/validation/etc)
Across these themes:
* links to best practices and graphs
* historical annotations on why this is written (documenting the context be through links or collapsable texts).
--
Karl Dubost
http://www.la-grange.net/karl/
Received on Thursday, 23 May 2013 15:04:24 UTC