Add slug to speakers xml export (proposal) #266
Conversation
|
IMO adding the speaker info directly in |
| @@ -68,7 +68,7 @@ xml.schedule do | |||
| xml.feedback_url event[:feedback_url] | |||
| xml.persons do | |||
| event[:speakers].map(&$to_speaker).each do |speaker| | |||
| xml.person( speaker[:name], {:id=>speaker[:person_id]} ) | |||
| xml.person( speaker[:name], {:id=>speaker[:person_id],:slug=>speaker[:slug]} ) | |||
There was a problem hiding this comment.
Could you please add:
:avatar=>speaker[:avatar],:biography=>speaker[:biography]
(only based on documentation, I haven't tested it, can do it later this week)
There was a problem hiding this comment.
I'm not sure that is the right solution, because it would duplicate biographies for speakers. Moreover, I would not store the biography as an attribute.
Perhaps we could add a section. xxxyyyy, so both can be linked?
There was a problem hiding this comment.
Ah, you are right, although I am not sure how big of a problem duplicates are. Probably the change would need to be backwards-compatible, so speaker name can stay and a new section by person_id or code (I can look into this on the weekend).
|
Wait, is Pretalx is using Ruby - oh cool, perhaps I can even help to improve the PR:) |
No the website is using Ruby, pretalx is written in Python. But hey, we can use hands on the website as well, perhaps even more. |
Adds the slug of speakers to the xml export. Can be used to fetch user information on the website for apps.
Example file for 2024:
schedule.xml.zip
speakers can be reached by this slug:
https://fosdem.org//schedule/speaker/
This is just a proposal, we might as well add all speaker information inside the xml as well under a new section. Not sure what would be most appropriate.