Refactor to remove dajaxice.
Modified the URLs that address schedules:
- urls now always start with /agenda, removing the mix of /agenda and /schedule prefixes
- urls to a given schedule include the schedule owner (by email address)
Corrected issue that prevented deleting sessions.
Changed comment mechanism in timeslot_edit.js
Migration to change the email address for (System)
Fixes bug #1426
Commit ready to merge
- Legacy-Id: 8229
* Removes the pattern of using ScheduledSession m2m objects with one of the relationships left as None
* Improves scheduled session state handling
* Simplifies sending email to scheduled session requestors
* Improved timeslot purpose and room editing
* Improved access controls to editing forms
* Better test coverage for the meeting views
* Improvements to the javascript driven by prototyping automated tests
* Better initialization of a new meeting
On the session request form:
- Allows specifiying room resources (projectors, meetecho)
- Allows specifying what people must be present
On the schedule editing page:
- correctly calculates conflict levels
- displays conflicts in and out of each session separately
- italicizes BoFs
- shows resource and people conflicts
Adds automated placement as a management command
Commit ready for merge.
- Legacy-Id: 7561
Changed the URL for some acoount settings from /cookies to /account/settings.
Fixes ticket #806,
- Legacy-Id: 7385
Note: SVN reference [7380] has been migrated to Git commit af302582b0a9f36941ef15b39bf52c2a51fbafe1
(-r5465:HEAD from branch/iola/shimfree). Copying relevant
commit messages here:
- Deleted dead code in many places.
- Renamed id-something to draft-something, make the "is
this eligible for expiration" logic clearer
- Added a name for IPR search URL
- Revamped the ballot popup view
- URL reversed the IPR search link instead of hardcoding it
- Cleaned up search views and remove dead code, port them to the new DB
schema, hack related views in iesg/ and wginfo/ to use the new search
interfaces, avoid camelCase in search GET parameters (with
backwards-compat fallback), add some simple search unit tests, remove
caching from views_search.py index pages as they're now pretty fast to
generate, rewrite ballot popup JS, regularize some CSS classes to use
hyphen-notation rather than camelCase, move some of the search
templates to doc/.
idrfc/ now mostly contains some wrapper code still in use by other
subdirs, some ported code not yet moved, and dead code.
- Fixed output bug in test crawler and print referrer upon errors so it's
easier to figure out where a link came from
- Added /doc/in-last-call/ to crawler, report original page as referrer in
a redirect chain rather than intermediate URL
- Ported idindex to new schema, speed them up, add tests, refactor index
page in views_search to share code with the text index file, get rid
of some special-case idindex filters from ietf_filters, move
"/drafts/" redirects to a file in /doc/
- Ported /idtracker/status/ and /idtracker/status/last-call/ overview of
drafts in IESG process to new schema in /doc/iesg/ and
/doc/iesg/last-call/
- Added redirects for all of /idtracker/*, removed all view code and other
dead code from idtracker/
- Removed the idtracker sitemap indexing drafts - in its current form,
it adds nothing of value to the HTML-based /doc/all/ view, and it's
pretty slow
- Ported idtracker feeds to new schema, move them to doc/, cleaned up
idtracker/ - only templatetags/ietf_filters and proxy code is left
- Legacy-Id: 5836
* Skip IANA - Review Needed and Version Changed - Review Needed changes from
IANA as it turns out that the Datatracker is the authoritative source on
these states. Also improve logging so that the raw JSON from IANA is
dumped, the parsed JSON on imported changes is dumped and we write to
syslog before starting a sync script in the notification view.
* Only add charter state change link when chartering, it doesn't make sense
for an approved charter. Fixes#861.
* Don't display group.comments on the charter document page. Apparently
group.comments have been used by the Secretariat in the past for
chartering comments, but it's not possible to edit the field and the whole
thing doesn't make sense from a modelling perspective - a feature like
this should probably use the note field on the charter. Fixes issue
#1048.
* Don't crash if an attachment has been created already, just reuse it -
this case shouldn't actually happen, but apparently sometimes does,
probably due to a concurrency issue
* Add link to charter pages from the milestones editing page (besides the
cancel button), fixes#1044.
* Special-case proposed working groups with respect to milestones, they get
the charter milestones on the WG charter page rather than the current set
* Show approved milestones on /doc/charter-xyz/ page if the charter is
approved instead of only showing proposed milestones for proposed charters
- Legacy-Id: 5812
Note: SVN reference [5794] has been migrated to Git commit a603b8e056
Note: SVN reference [5800] has been migrated to Git commit 0f69f87a56
- Legacy-Id: 5786
Note: SVN reference [5614] has been migrated to Git commit 7e0e027149a37e2fac0b2809e8a18c896f660687
Note: SVN reference [5622] has been migrated to Git commit bde631c87ffd2ce5a93fe3c0559aafef04d23b1f
page in views_search to share code with the text index file, get rid
of some special-case idindex filters from ietf_filters, move
"/drafts/" redirects to a file in /doc/
- Legacy-Id: 5634
discrepancies report for seeing differences between the
Datatracker/RFC Editor/IANA, add tests of IANA/RFC Editor integration,
add script for weekly discrepancies emails
- Legacy-Id: 4851
/doc/<doc-name>/charter/ since they now all concern the actual charter
documents rather than the WG (this removes some redundant code).
- Legacy-Id: 4271
Setting user cookies, and settable expires soon and new tags
in id/rfc list.
- Legacy-Id: 2634
Note: SVN reference [2619] has been migrated to Git commit ddd9b6fe4d702af5e9b132621a47f59fe2f36b4e
* announcements -> ann
* liaisons -> liaison
* idindex -> drafts
* mailinglists -> list
I checked the tests and used a link checker locally, so hopefully
the fallout will be minimal.
- Legacy-Id: 657
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
in (unless it's a forced login) will be the (incomplete) "my" view.
Username and logout link are in the upper right corner while logged
in.
- Legacy-Id: 163
