Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Links to meetecho aren't appearing for some sessions of the ietf group #4745

Closed
rjsparks opened this issue Nov 10, 2022 · 3 comments · Fixed by #5038
Closed

Links to meetecho aren't appearing for some sessions of the ietf group #4745

rjsparks opened this issue Nov 10, 2022 · 3 comments · Fixed by #5038
Assignees

Comments

@rjsparks
Copy link
Member

(Probably related to session purpose).
At IETF 115, links for meetecho did not automatically appear for the Newcomers session, IEPG, the wgchairs forum, or the host speaker series.

The secretariat entered alternate online coordinates, which shouldn't have been necessary - it resulted in three buttons suddenly appearing - the manually entered coordinates and the automatically generated coordinates that were not present before. In one case (host speaker series), because things were done at meeting speed, those links were different.

wgchairs might be different from the others as it was (I think) created as group emodir (which is right), but the links saying emodir rather than wgchairs caused some consternation.

@jennifer-richards
Copy link
Member

jennifer-richards commented Jan 25, 2023

The decision whether to show the buttons at all is here

if (item.flags.showAgenda || ['regular', 'plenary'].includes(item.type)) {

The showAgenda flag comes from

"flags": {
"agenda": True if item.session.agenda() is not None else False,
"showAgenda": True if (item.session.agenda() is not None or item.session.remote_instructions or item.session.agenda_note) else False
},

which is why setting the remote_instructions value causes buttons to appear.

The standard buttons come from the Room where the session is being held. The meetecho links are generated using the UrlResource with name=='meetecho', which (for all rooms) is https://meetings.conf.meetecho.com/ietf{meeting.number}/?group={group.acronym}&short={short}&item={order_number} with the bracketed expressions interpolated.

@jennifer-richards
Copy link
Member

Question: what exactly tneeds to change here? The simplest thing to do would be to turn on the standard meetecho links for these sessions. Assuming the Room data are similar to IETF-115 in the future, that will add video stream, audio stream, and onsite tool links. These will be formatted like

  • Host Speaker Series
    • https://meetings.conf.meetecho.com/ietf115/?group=ietf&short=&item=3
  • New participants' overview
    • https://meetings.conf.meetecho.com/ietf115/?group=emodir&short=&item=2
  • IEPG
    • https://meetings.conf.meetecho.com/ietf115/?group=iepg&short=&item=1
  • WG Chairs Forum

Are these ok? It doesn't address the consternation about the wgchairs URL containing emodir, but that could be at least partly addressed by giving the session a short name (which would show up in the URL where there's currently a blank value for the short query parameter).

@rjsparks
Copy link
Member Author

standard meetecho links is what I think is what we are asking for.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants