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

Better FOSS4G Europe 2024 schedule #359

Merged
merged 5 commits into from
Jun 28, 2024
Merged

Better FOSS4G Europe 2024 schedule #359

merged 5 commits into from
Jun 28, 2024

Conversation

Zverik
Copy link
Contributor

@Zverik Zverik commented Jun 19, 2024

The current version has only the main event schedule and no speaker names. The new one, sourced from here, merges main event, workshops, birds of feather, all side events, and OGC Innovation Days into one.

I have also added locations for all venues.

Copy link

github-actions bot commented Jun 19, 2024

New: FOSS4G Europe 2024 (extended)
Removed: openSUSE Conference 2024
File passed validation! \o/

@Wilm0r
Copy link
Owner

Wilm0r commented Jun 19, 2024

Ooh nice, thanks for the contribution :D Did you scrape the website to generate this version yourself?

One issue is that replacing schedules in Giggity is a little messy, especially it's hard to preserve selections. I'm trying to improve this but that work isn't done yet.

Just in case anyone has talks selected already they should be able to find those back. Maybe it's best to mark your schedule with a " (extended)" title suffix?

(Once my work is done we'd be able to do better here, though even then of course only if the extended schedule does use the exact same id's/uuid's for talks, etc.)

@Zverik
Copy link
Contributor Author

Zverik commented Jun 19, 2024

I've just used my schedule merging tool, just like for sotm_2019 ,sotm_2021, sotm_2022, sotm_eu_2023.

The base component is of course the same xml (actually json, because xml misses speakers), so all the ids, codes, slugs are preserved.

The conference is in two weeks, and Giggity app was promoted second to the official conference app (you know the one, EventFahrplan or something, severely lacking), so I don't think anybody would be affected by the change.

Though if you want I can mark it with "(extended)", but that may bring more confusion.

@Wilm0r
Copy link
Owner

Wilm0r commented Jun 25, 2024

The problem is that if you don't add a tag, people will have two identically named entries for this conference in their menu which is pretty confusing. So we really need a tag, even though that's indeed also ugly. That's why I'm hoping to fix that behaviour in some future Giggity version.

@Wilm0r
Copy link
Owner

Wilm0r commented Jun 25, 2024

Maybe the best thing to do is actually to keep the existing file as-is but with a " (short/old schedule)" tag.

There's just no great way to deal with this when Giggity uses the URL as the primary key for the event and won't delete anything from its internal database just because the URL changed/disappeared from the menu seed file.

@Zverik
Copy link
Contributor Author

Zverik commented Jun 25, 2024

Right, I've understood. URL is part of the key, so there's no good way of changing it. Happens :)

I've reverted the original schedule and renamed mine, adding "(extended)", as you suggested earlier.

@Zverik
Copy link
Contributor Author

Zverik commented Jun 28, 2024

Could you please merge it soon? I'd like to promote the extended schedule in the app among the participants :)

@Wilm0r Wilm0r merged commit a7ea74d into Wilm0r:master Jun 28, 2024
1 check passed
@Wilm0r
Copy link
Owner

Wilm0r commented Jun 28, 2024

Oof, thanks for the ping! Not sure how I missed your last update, either bad luck or that annoying fastmail bug again where it sometimes wrongly marks emails as read. :|

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants