altf4arnold/datatracker
1
0
Fork 0
Code Issues Pull requests Actions 3 Packages Projects Releases Wiki Activity

Updated PLAN

Browse source 
- Legacy-Id: 17225
This commit is contained in:
Henrik Levkowetz 2020-01-13 17:14:06 +00:00
parent d2b2bb1417
commit 87eb0fb640
1 changed files with 10 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
PLAN
View file

@ -20,14 +20,21 @@ Planned work in rough order
* Polish the htmlization pages, making the style identical with tools.ietf.org.
* Rework email sending so that all emails sent by the datatracker, except for
logging and failure emails sent to ADMINS, are captured as a Message object.
* Investigate adding code to trigger test exceptions for template variables
that don't successfully resolve. A small trial run of this has indicated
that most instances that trigger such exceptions would benefit from better
resulution -- i.e., in the trial, it didn't seem that we to any greater
extent have template code that is written to rely on failure to resolve
rendering as nothing.
* Investigate making RFCs first-class document objects to faciliate being
able to model BCPs that represent groups of RFCs properly. Then fix the rfc sync
script to update BCP aliases when changes occur changes (a BCP points to new
RFC numbers)
* Rework email sending so that all emails sent by the datatracker, except for
logging and failure emails sent to ADMINS, are captured as a Message object.
* Review and change the draft submission and handling code to deal with UTF-8
instead of ascii before upload of utf-8 drafts should be permitted.
(This may fall out for free with the Python 3 transition).