-
Notifications
You must be signed in to change notification settings - Fork 393
Historic: Documenting the evolution of the proceedings tool proceedings16
Ryan - Introduction section contents
- Agenda: link
Update IETF Overview template to use historical roles
M Richards suggested having links on each group proceedings page to previous / next meeting
Ensure the links to the group goto the right grouphistory object.
Add a section for groups that didn't meet.
Reference: http://www.nostrum.com/~rjsparks/draft-sparks-genarea-proceedings-materials-pre00.txt
(Done) : Robert - Start with /meeting/96/proceedings (work out access permissions) - copy? of materials templates to start with, then evolve them. Watch for opportunities for reuse instead of copy as much as possible.
(Done) : Load bluesheets for recent N meetings into the datatracker (migration created to load 95 and 96).
(Done) : Put recordings and blue sheets onto the the proceedings
(Done) Add "proceedings due dates" to Meeting similar to the submission cutoff dates. Make sure the secr meeting edit form is updated to allow manipulating them.
(Done) Add a "proceedings finalized" bit to Meeting. Add a "finalize meeting" button to the proceedings page when viewed as secretariat. When pressed, set the finalized bit, and modify the sessionpresentation objects for drafts as described in the below draft. The warning badges (like "no minutes") should not appear when the finalized bit is set.
(Done) : Ryan - once proceedings page is up add Introduction
(Done) : Ryan - Acknowledgements: TextField on meeting
(Done) : Put status updates on the proceedings
(Done): Modify the bluesheet uploader to create bluesheet document objects and associate them with sessions. Form needs to allow uploader to select a session. Creation logic can be taken from the migration for 95 and 96 above.
(Done): IETF Overview. Initial implementation with static template complete. Next step add historical roles.
(Done): Create bootstrap version of materials upload page, https://datatracker.ietf.org/secr/proceedings/96/6lo/. Ultimately it will be accessed from the Upload Edit Materials link on the session page, https://datatracker.ietf.org/meeting/96/session/rtcweb/. This will facilitate the move to supporting attaching materials to specific sessions, rather than by group
(Done): Allow for groups with multiple sessions to have an agenda per session and minutes per session.
(Nothing to do): Put area groups on the proceedings page. (They're already there - just not in their own section, which is ok.)
(Done): Ryan Introduction Progress Report. Optimized to run on demand (2-4 seconds)
(Done): Ryan Introduction Attendees: import to dbtemplate. UPDATE: Matt has implemented an export from registration
Should bluesheets be Documents? We don't revise them, they don't have authors. The work already done proves that we can make it work if they are Documents, but is there a better way to model them?
Should we include Jabber Logs, Mail Archives https://www.ietf.org/proceedings/95/httpbis.html. No - this material is available from the charter page for the group