Updated PLAN
- Legacy-Id: 15045
This commit is contained in:
parent
a9fbea113b
commit
5733db6c75
11
PLAN
11
PLAN
|
@ -16,16 +16,7 @@ Planned work in rough order
|
|||
could have been done with only table edits if there hadn't been so much code
|
||||
using type_id lists and features needing code changes).
|
||||
|
||||
* GDPR related: a) Add SimpleHistory for Person in order to have traceability
|
||||
of changes to person records. Include client IP address. b) Make sure all
|
||||
parts of a person's record is reflected on the account page and can be
|
||||
updated/corrected. c) Any form update requires a checkbox filled in which
|
||||
signifies consent to use the data on the IETF website. d) The submission
|
||||
tool also requires a consent checkbox for usage of personal data contained
|
||||
in the uploaded draft. e) There should be a link (in the footer?) to a page
|
||||
common for the IETF, probably, that describes how to request purging your
|
||||
personal information from the datatracker. Actual purging can be done trough
|
||||
the Django admin interface, no new software required.
|
||||
* GDPR related changes
|
||||
|
||||
* Reworked UI and refactored backend for the scretariat meeting scheduling
|
||||
tool.
|
||||
|
|
Loading…
Reference in a new issue