1 ==================================
2 :Title: <REQUIRED: proposal title>
3 ==================================
5 :Author: <REQUIRED: list of authors' real names and optionally, email addrs>
6 :Discussions-To: docutils-develop@lists.sf.net, <enhancement ticket URL>
7 :Status: <REQUIRED: Draft | Active | Accepted | Provisional | Deferred | Rejected | Withdrawn | Final | Superseded>
8 :Type: <REQUIRED: API | Informational | Process>
9 :Created: <date created on, in dd-mmm-yyyy format>
10 :Docutils-Version: <version number>
11 :Replaces: current policy/API document
18 .. A short (<~200 word) description of the technical issue being addressed.
24 .. Clearly explain why the existing specification is inadequate to
25 address the problem that the proposal solves.
31 .. Describe why particular design decisions were made.
37 .. Describe the syntax and semantics of any new feature.
40 Backwards Compatibility
41 =======================
43 .. Describe potential impact and severity on pre-existing code.
49 .. How could a malicious user take advantage of this new feature?
55 .. How to teach users, new and experienced, how to apply the proposal to
59 Reference Implementation
60 ========================
62 .. Link to any existing implementation and details about its state, e.g.
69 .. Why certain ideas that were brought while discussing this proposal
70 were not ultimately pursued.
76 .. Any points that are still being decided/discussed.
82 .. A collection of URLs used as references through the proposal.
88 This document is placed in the public domain or under the
89 CC0-1.0-Universal license, whichever is more permissive.
97 sentence-end-double-space: t