Skip to content

[WIP] Berlin schedule work #2399

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

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from
Draft

[WIP] Berlin schedule work #2399

wants to merge 5 commits into from

Conversation

mxsasha
Copy link
Contributor

@mxsasha mxsasha commented Jul 16, 2025

This PR is to play with possible schedules, having been fixed for the missing writing day. The fixes in the templates will have to be merged into main even if the rest if this PR is not.

Also note the flags set in the config - notably, you can't set flaghasschedule without also setting flagspeakersannounced, or the schedule key will be missing from the context.


📚 Documentation preview 📚: https://writethedocs-www--2399.org.readthedocs.build/

@plaindocs
Copy link
Contributor

Thanks @mxsasha

Mostly I propose we start later on both days :-D. Probably something like

  • intro at 9:30 on Monday, and first talk at 9:30 Tuesday.
  • which would also bump lunch later, which I think is a good thing
  • we should probably remove the social till we know how we're doing that?

Direct link to the current status of the schedule.

@ericholscher @katiejano @MissMikeyMay ?

@ericholscher
Copy link
Member

ericholscher commented Jul 21, 2025

We always started Prague at 10am I believe, but don't feel too strongly.

The big change we discussed in Portland was making a 5 minute Q&A, instead of 10, and that isn't reflected here.

@plaindocs
Copy link
Contributor

@ericholscher do we want to switch to 5 min Q&A + 10 min break, keeping the spacing the same?

@ericholscher
Copy link
Member

I think that is what we were imagining. If the Q&A is crashing it, it can go a couple minutes long, but I think setting the expectation of being five minutes is a good one.

@plaindocs
Copy link
Contributor

Sponsor intros after lunch or before lunch? @ericholscher @katiejano I think after right?

@katiejano
Copy link
Contributor

katiejano commented Aug 7, 2025 via email

@plaindocs
Copy link
Contributor

Right, I'm asking what we want.

@ericholscher
Copy link
Member

Earlier is better IMO. But it's hard to figure out what will feel best for attendees. I think after the break is better than having sponsors in the way of food... but we need to herd people back effectively. Easier for that with a break than with lunch.

@plaindocs
Copy link
Contributor

How about after the lightning talks?

@ericholscher
Copy link
Member

I'd be worried the lightning talks might be shorter than advertised, so the time we tell the sponsors will have a weird gap after the lightning talks before the break. I think after the first snack break is the best time? It's a firm time slot we control.

@katiejano
Copy link
Contributor

It's currently after the Speaker Talk 2. I could move it to after the Coffee Break and directly before Speaker Talk 3, which may feel more in the flow versus after a Q&A. I'd suggest keeping it in Monday morning. It's already a full afternoon.

@plaindocs
Copy link
Contributor

Yep, then I think we're all in agreement, after coffee break on Monday morning.

@ericholscher
Copy link
Member

I think we definitely want more than 30 mins between doors and conf starting. That is not enough time to register everyone and get the tours started at 9:15.

@katiejano
Copy link
Contributor

@ericholscher I don't think the schedule has been updated with the most recent changes. The Master doc has doors to venue at 8:30, WW tour at 8:45, and doors to auditorium at 9:00. As I'm writing this out, I am wondering if we should do doors to venue at 8:00 and WW tour at 8:30 to give us a little more space.

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

Successfully merging this pull request may close these issues.

4 participants