fosdem-companion-android
fosdem-companion-android copied to clipboard
Display the speaker's bio and picture
Not sure if the API you're using actually provides this information, but I would find it helpful to learn more about the speaker of a given session when tapping their name. Currently, you only show a list of sessions related to that speaker. Thanks!
I wanted to do this for a long time but unfortunately I don't have access to this information. At least there is a link to the website where you can see more info about the speaker.
There is still no speaker information in the schedule file, but I'll push to add this for FOSDEM 2025.
The only way now I can come is to parse https://fosdem.org/2024/schedule/events/ page and create a map of https://fosdem.org/2024/schedule/speaker/* links to names (and sessions in case of multiple speakers of same name).
So
<tr>
<td><a href="/2024/schedule/event/fosdem-2024-1953-using-code-generated-by-ai-issues-misconceptions-and-solutions/">Using code generated by AI: issues, misconceptions and solutions<br/><i></i></a></td>
<td><a href="/2024/schedule/speaker/7FMT97/">Andrew Katz</a></td>
<td><a href="/2024/schedule/room/ub2252a/">UB2.252A (Lameere)</a></td>
<td><a href="/2024/schedule/day/sunday/">Sunday</a></td>
<td>13:45</td>
<td>14:15</td>
<td>
</td>
<td>
</td>
</tr>
merged with
<event id="14133">
<start>13:45</start>
<duration>00:30</duration>
<room>UB2.252A (Lameere)</room>
<slug>fosdem-2024-1953-using-code-generated-by-ai-issues-misconceptions-and-solutions</slug>
<title>Using code generated by AI: issues, misconceptions and solutions</title>
<subtitle></subtitle>
<track>AI and Machine Learning devroom</track>
<type>devroom</type>
<language>en</language>
<abstract><p>As ever, technology has raced ahead of the law. What are the copyright issues with ingestion of training data, configuration and transfer of models, and the generation and use of code? Can GPL code inadvertently be incorporated into your non-GPL codebase? Who owns the copyright in generated code? Andrew Katz, a lawyer specialising in open source and AI, will explain the issues, and consider potential solutions.</p></abstract>
<description></description>
<persons>
<person id="1852">Andrew Katz</person>
</persons>
<attachments>
</attachments>
<links>
</links>
</event>
Would give info that speaker #1852 name is "Andrew Katz" and his bio page is "/2024/schedule/speaker/7FMT97/".
No idea does it make sense to follow it.
@hrw Note that this logic doesn't work if two speakers have the same name (which is luckily not the case this year).
Scraping does the job but it would be easier to use the YAML export file directly if it was made available publicly. This is the file used as source of truth to generate both the static FOSDEM website and XML schedule file.
Note that currently the speakers URL contain an id that's not the same as the numeric id in the schedule file. This is the id used internally by Pretalx. I already asked if it was possible to go back to using slugs in speakers URLs as it was the case before.
As long as Joe Doe (id 123) does not share talk with Joe Doe (id 234) they can be mapped by talk they give.
But it does not make things easier as html parsing can be worse than xml.