I think it was brought up on the techspec mailing list that we
do have a:
Potential requirement: We need a source code control system
into which the source material for an IETF spec is
created/mainatained.
The IETF Technical Publisher must make any changes to
the source material and ensure that an up to date source
is checked into the source code control system when an
RFC is published.
We can discuss which forms of source files would need to be handled.
But one way or another I think we really need to get an up to date
source file for all RFCs, so that future fixes/changes/additions/
extensions can easily be made, either by the same author/editor or
by new WG authors/editors.
Bert
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Stephen Hayes (TX/EUS)
> Sent: Friday, January 13, 2006 22:03
> To: [email protected]
> Subject: [Techspec] New version of mankin-pub-req available
>
>
> The -02 version of the technical publication requirements is
> available at
> http://www.ietf.org/internet-drafts/draft-mankin-pub-req-02.tx
> t. It is an extensive rewrite of the -01 version with an eye
> to taking a more systematic approach. The new version is
> basically a laundry list of requirements (both current and
> potential) against a technical publisher. The goal is to
> provide a framework in which we can decide what the IETF
> wants a technical publisher to do and what level of
> performance we want to see.
>
> Comments eagerly awaited.
>
> Stephen Hayes
>
> _______________________________________________
> Techspec mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/techspec
>
_______________________________________________
Techspec mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/techspec
