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. In addition an additional requirement should be added along the lines of: o Potential Req-TIMEFRAMES-3 - The IETF technical publisher should have a goal of an average time for completing the pre-approval editorial review of no more than 2 weeks and at least 98% of all documents should be reviewed within 4 weeks. The review interval starts when the editorial review is requested and ends when the review results are provided. This is to prevent simply shifting the long queuing delay from the post-approval phase to the pre-approval phase. I would also propose that we add text prohibiting stylistic changes in the post-approval editing (but permit it in pre-approval editing). Stephen Hayes _______________________________________________ Techspec mailing list [email protected] https://www1.ietf.org/mailman/listinfo/techspec
