owner:jennifer@painless-security.com resolution_fixed type_enhancement | by rjsparks@nostrum.com
Right now, the proceedings pages do not contain all of the information they should - several bits of information are left attached to the meeting pages in the wagtail server and may or may not be linked from the proceedings pages.
This places a maintenance burden on the wagtail server, where changes in page structure can lead to unintended changes in what should be a stable representation of what happened at a past meeting.
The secretariat would like to have additional information captured. Some managed at any point in the meeting lifecycle, and some captured at "finalization" time.
Specifically, a meeting should have an associated set of sponsors - with the sponsor role, and logo. Hosts would show on the main agenda page. Other types of sponsors would show on a derived sponsor page.
A meeting should have a set of proceedings_materials documents. These would be listed on the proceedings pages, in order. See the attached sketch. The uploaded content backing the document would be pdf files. The Host Speaker Series and Social Event links from the sketch are examples of the types of documents that would have been associated with IETF 106. There might also be a supporters page in addition to the derived page showing names and logos above that provides additional content specific to the meeting.
A meeting should also have a set of labelled external urls - for the sketch for 106, an example would be the link to the meeting wiki.
The rest of the links in the sketch already exist, but some are renamed: attendees becomes participants, progress report becomes activity report.
Issue migrated from trac:3147 at 2022-03-04 08:07:12 +0000
owner:jennifer@painless-security.comresolution_fixedtype_enhancement| by rjsparks@nostrum.comRight now, the proceedings pages do not contain all of the information they should - several bits of information are left attached to the meeting pages in the wagtail server and may or may not be linked from the proceedings pages.
This places a maintenance burden on the wagtail server, where changes in page structure can lead to unintended changes in what should be a stable representation of what happened at a past meeting.
The secretariat would like to have additional information captured. Some managed at any point in the meeting lifecycle, and some captured at "finalization" time.
Specifically, a meeting should have an associated set of sponsors - with the sponsor role, and logo. Hosts would show on the main agenda page. Other types of sponsors would show on a derived sponsor page.
A meeting should have a set of proceedings_materials documents. These would be listed on the proceedings pages, in order. See the attached sketch. The uploaded content backing the document would be pdf files. The Host Speaker Series and Social Event links from the sketch are examples of the types of documents that would have been associated with IETF 106. There might also be a supporters page in addition to the derived page showing names and logos above that provides additional content specific to the meeting.
A meeting should also have a set of labelled external urls - for the sketch for 106, an example would be the link to the meeting wiki.
The rest of the links in the sketch already exist, but some are renamed: attendees becomes participants, progress report becomes activity report.
Issue migrated from trac:3147 at 2022-03-04 08:07:12 +0000