|
From: Günter M. <mi...@us...> - 2025-04-09 15:18:39
|
An updated patch. Attachments: - [0001-Set-up-enhancement-proposals-in-developer-documentat.patch](https://sourceforge.net/p/docutils/feature-requests/_discuss/thread/7144ba7ba2/bccf/attachment/0001-Set-up-enhancement-proposals-in-developer-documentat.patch) (27.4 kB; text/x-patch) --- **[feature-requests:#111] Docutils Enhancement Proposals** **Status:** open **Group:** Default **Created:** Thu Feb 13, 2025 10:05 PM UTC by Günter Milde **Last Updated:** Fri Feb 14, 2025 12:52 AM 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 doc...@li... 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. |