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

Updated PLAN

Browse source 
- Legacy-Id: 12946
This commit is contained in:
Henrik Levkowetz 2017-03-01 14:03:53 +00:00
parent 348591a4bb
commit ef1b59ec8c
1 changed files with 14 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
PLAN
View file

@ -26,14 +26,9 @@ Planned work in rough order
* Add a bullet for the IESG request for a "recent ballots" page (IESG request) * Add a bullet for the IESG request for a "recent ballots" page (IESG request)
* Introduce and API for Meetecho to use to associate recordings with sessions * Introduce an API for Meetecho to use to associate recordings with sessions
(and perhaps automate making copies of those videos) (and perhaps automate making copies of those videos)
* Introduce the use of email.header.Header() in order to be able to handle
non-ascii names in email From:, To: and Cc: fields.
* Add support for IAB Programs
* Revisit photo uploads: Add photo upload for people with roles. Add * Revisit photo uploads: Add photo upload for people with roles. Add
photos to wg pages and group overview pages. photos to wg pages and group overview pages.
@ -42,10 +37,23 @@ Planned work in rough order
on multiple floors (probably means modelling break areas the same way on multiple floors (probably means modelling break areas the same way
as other sessions, and removing the break_area char_field on Meeting. as other sessions, and removing the break_area char_field on Meeting.
* Transition to Python 3. This will make it easier to add add support for
internationalsed email, and also other i18n enhancements.
* Add support for internationalised email addresses according to RFC 6531 * Add support for internationalised email addresses according to RFC 6531
when sending email (this is not supported by smtplib under Python 2.7, when sending email (this is not supported by smtplib under Python 2.7,
so will need support code in the application until we migrate to Python 3.5) so will need support code in the application until we migrate to Python 3.5)
* Transition to PostgreSQL. This will make it easier to start using
timezone-aware timestamps throughout the code, which will make it easy
to present localized times on web-pages. It will also provide additional
tools for performance analysis
* Transition to using timezone-aware timestamps. Migrate database timestamps
to be timezone-aware. This means converting all timestamps to PST8PDT,
except for meeting-related timestamps, which use the meeting.time_zone.
Once done, set USE_TZ to True in settings.
* Performance analysis of database table and index setup * Performance analysis of database table and index setup
* Review and change the draft submission and handling code to deal with UTF-8 * Review and change the draft submission and handling code to deal with UTF-8