- Fixed layout issue on schedule editing page in Chrome
- Fixed errant display of text in unscheduled group bar
on the schedule editing page
- Changed the instruction text on the special requests
field of the session request form
From rcross@amsl.com:
- Improved scheduling of non-session items
- Fixed issue with layout of the new notifications page
- Fixed crash on notifications page
- Legacy-Id: 7644
Updates and bugfixes to the agenda editing features
* 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
- Legacy-Id: 7628
Note: SVN reference [7561] has been migrated to Git commit 1221f79af9
* 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
out nomcom.js is included in the wrong pages, and on the pages it is
actually useful in, it's obsolete, so delete it together with the
obsoleted AJAX view and the other JS left-over cruft in nomcom/, this
fixes an include 404 and removes the remaining dependency on
jquery-1.5.1 apart from the Secretariat tools
- Legacy-Id: 7097
meeting AJAX code is using PUT instead of POST (even if it's not
PUT'ing in the literal sense but POST'ing). Theoretical discussions
aside, Django has poor support for PUTs turned POSTs so rewriting them
removes the need for a couple of hacks, and makes it easier to test.
- Legacy-Id: 7067
duplicated code, make sure the custom form widgets escape their input.
There's still a bit of custom proxying going on in the IETFHM class
hierarchy.
- Legacy-Id: 6794
- Rename IdSubmissionDetail to Submission
- Rename various submission fields to correspond to the conventions in
the new schema
- Use a name model for the states instead of IdSubmissionStatus
- Drop the TempIdAuthor model which is based on splitting up author
names
- Add a simple textual SubmissionEvent for tracking events in the
lifetime of a submission
- Delete a bunch of obsolete fields
- Make sure all submission have an access key so we can depend on it
- Add state for when approval is needed from previous authors
A couple of migrations take care of transforming the
IdSubmissionDetail and moving data over/cleaning it up.
Also revamp the submit view code:
- Make form code do validation/cleaning only so there's a clear
separation of concerns
- Reduce uses of inheritance that made the code hard to follow -
forms now don't inherit from each other, views don't call each other
but instead reuse common utilities, templates share CSS/utilities
instead of relying on inheritance
- Move email rendering/sending to separate file
- Drop the in-grown terminology use (auto post vs. manual posts)
- Make the status page explain who is emailed for what purpose
- Add history table with recorded events
- Make the status page handle its post actions by itself instead of
duplicating most of the setup logic in a number of simple views
- Fix a couple of minor bugs and handle some edge cases better
- Expand tests with a couple of more cases
Possibly the submit tool could still use more help text added to
explain the process, ideally what's explained in the tool instructions
page should be inlined or self-evident.
- Legacy-Id: 6714
replaced the noTable block construct with start/end table_content blocks
in order to not have to open and close tables in different blocks, and
not have empty tables lying about.
- Legacy-Id: 6439
additional tweaks from henrik: Added the capability to search for all kinds
of documents in the main datatracker search page. Fixes bug #838.
- Legacy-Id: 5926
Note: SVN reference [5898] has been migrated to Git commit b14a8d0cee
