Two (fairly distinct) points...
Spencer
From: "Brian E Carpenter" <[EMAIL PROTECTED]>
Stephen Hayes (TX/EUS) wrote:
mankin-pub-req currently has requirements for both pre approval
(Potential Req-PREEDIT-1) and post approval (Req-POSTEDIT-1). We need to
decide which requirements stay and which ones go.
I think both requirements are needed, however each document should only
have to pass through either pre-approval editing or post-approval editing
but not both. This will allow the IETF to migrate to a methodology using
pre-approval editing over time. Usage of pre-approval editing should be
encouraged.
What about cases where (e.g. due to major issues during IESG processing),
significant new text has appeared? I think we need the option of a post
approval edit pass in such cases, but it should be the exception.
OK, this is the IETF side of techspec, which is likely a newtrk
responsibility, but ... if a working group forwards out a working
group-consensus draft, and then "significant new text appears", we probably
need more than a "post approval edit pass" in most cases, don't we? Given
that this stuff really *should* be running through the working group before
publication, why do we need a post-approval edit pass?
I agree that significant new text during approval processing should be the
exception.
I would also propose that we add text prohibiting stylistic changes in
the post-approval editing (but permit it in pre-approval editing).
Yes, but even in pre-approval I see no reason why editing should change
the tone, for example by removing intentional informality.
Agree, and suggest that the wording say something like "proposed" when we
talk about stylistic changes, so that it's perhaps more obvious that
stylistic changes aren't gating for document approval and/or publication -
if Brian and Elwyn spell the word as "colour" in their drafts, and don't
want to accept a proposed change from "colour" to "color", that's OK within
techspec.
Thanks,
Spencer
_______________________________________________
Techspec mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/techspec
