LiaisonUser, and EmailAddresses for a mapping to a PersonOrOrgInfo.
It doesn't yet import all groups or permissions; that'll be a
separate (repeatable) process.
The goal is to eventually eliminate completely the WgPassword and
LiaisonUser tables. IESGLogin could go too eventually, but that
requires schema changes, not just changes in the authentication
mechanisms.
- Legacy-Id: 616
served by the mailing list form so bookmarks to them are extremely
unlikely.
Remove trailing "?" from /idtracker/ entry; the redirect tool
strips off empty query strings.
Add ?cat=bugs to the send_email entry so the redirect will pass.
Skip the redirect test for the ballot, since there's an extra
(unused) query argument, filename=.
Add in all the query args that will get passed through the
redirect when searching for bgp-m, to make sure that they work
and to make the redirect test pass.
- Legacy-Id: 609
Add the year to the date field when it's not this year, using a new template tag "thisyear" which returns a boolean.
Also implement template tag "inpast" which I think could be useful for the meeting materials page.
- Legacy-Id: 599
* Don't sort by ballot ID.
* dictsort by filename within 'primary_flag' sets inside the template.
* Change myifchanged to not reset on the first cycle of a for loop.
* Introduce cyclevalue tag, to get the current cycle color from the cycle node itself instead of the context, since the context gets reset between for loops.
- Legacy-Id: 596
are the same as their cgi counterparts. Differences:
* The sections are ordered differently; the cgi has Active, Published, Expired, Withdrawn; the django has Active, Expired, Published, Withdrawn by IETF, Withdrawn by Submitter. Since the explicit ordering by the cgi was why it missed the "Withdrawn by Submitter" documents, I chose to keep the database-influenced ordering.
* The revision numbers for published documents are of the version that was published, not of the tombstone.
- Legacy-Id: 590
* It changes all the time, so database update lag will cause differences
* It changes all the time, so any diff file will be quickly outdated.
I've done extensive review of the whole set of differences between
the django code and perl code running on the same database and am
confident in the correctness of the django code.
- Legacy-Id: 589
belong in the apache document root, and will be served by the
django server if it's being run in test or development mode
according to SERVER_MODE.
- Legacy-Id: 566
assignment, it would actually happen when the mod_python thread was
initialized, so the value would drift away from being right.
Match the I-D tracker implementation by moving it to the first day of
the month in which the day that's 185 days ago lives.
- Legacy-Id: 565
