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

Updated PLAN

Browse source 
- Legacy-Id: 16751
This commit is contained in:
Henrik Levkowetz 2019-09-26 15:50:34 +00:00
parent 44296e1aae
commit 9827f62671
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
PLAN
View file

@ -9,13 +9,15 @@ Planned work in rough order
* Polish the htmlization pages, making the style identical with tools.ietf.org. * Polish the htmlization pages, making the style identical with tools.ietf.org.
* Wrap Trac in a docker container, in preparation for transition to running
the datatracker under Python 3. It doesn't look like Trac will be available
for Python 3 until January 2020 at the earliest.
* Investigate making RFCs first-class document objects to faciliate being * 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 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 script to update BCP aliases when changes occur changes (a BCP points to new
RFC numbers) RFC numbers)
* Revisit the review tool, work through the accumulated tickets.
* Complete the transition to Python 3. This will make it easier to add add * Complete the transition to Python 3. This will make it easier to add add
support for internationalsed email, and also other i18n enhancements. The support for internationalsed email, and also other i18n enhancements. The
code has now been made Python 2 / Python 3 compatible (as of release 6.99.0, code has now been made Python 2 / Python 3 compatible (as of release 6.99.0,