Hi Melinda,
Funny, but I agree.
To be honest at this point I'm sort of reflexively
anti-process-documents, unless there's an actual problem
that needs actual solution.
Which is why this isn't a process document.
The origin is a WG chairs Edu session. Turns out there was not a lot of clarity
among a bunch of WG chairs about what they did and why. My assumption is that
if the chairs needed some time to discuss this, the community might need that
as well.
The problem I am now hearing is that "the document lifecycle is not described
coherently in one place." That wasn't the problem I was aiming to solve, but
maybe enough others consider it is a problem.
Is this a tutorial?
Mainly. To quote...
NOTE: This draft is intentionally non-normative. It is meant as a
guide to common practice, rather than as a formal definition of
what is permissible.
Adrian