[docutils:feature-requests] #111 Docutils Enhancement Proposals
Günter Milde via Docutils-develop <[email protected]> Tue, 29 Apr 2025 19:58:21 -0000
| Newsgroups | gmane.text.docutils.devel |
|---|---|
| Message-ID | </p/docutils/feature-requests/111/3c6b39f0e9f6cad79f23258840723950437a6e00.feature-requests@docutils.p.sourceforge.net> |
- **status**: open-fixed --> closed-fixed - **Comment**: Enhancement proposals can now be reached under https://docutils.sourceforge.io/docs/eps/index.html. --- **[feature-requests:#111] Docutils Enhancement Proposals** **Status:** closed-fixed **Group:** Default **Created:** Thu Feb 13, 2025 10:05 PM UTC by Günter Milde **Last Updated:** Tue Apr 22, 2025 02:05 PM UTC **Owner:** nobody **Attachments:** - [0001-Set-up-enhancement-proposals-in-developer-documentat.patch](https://sourceforge.net/p/docutils/feature-requests/111/attachment/0001-Set-up-enhancement-proposals-in-developer-documentat.patch) (25.9 kB; text/x-patch) - [ep-001.html](https://sourceforge.net/p/docutils/feature-requests/111/attachment/ep-001.html) (26.7 kB; text/html) Set up a framework for *Docutils Enhancement Proposals* as a mechanism for proposing major new features, collecting community input, and documenting important design decisions. The *Docutils To Do List* and issue tickets on the project page are sufficient for small changes or issues with an obvious solution. However, we are missing a framework for complex cases with competing alternatives and for documenting the internal processes at the Docutils project. Attached are a draft specification and a patch implementing EPs in the developer documentation. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/docutils/feature-requests/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.