-
Notifications
You must be signed in to change notification settings - Fork 519
Berlin schedule #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
Berlin schedule #2399
Conversation
Thanks @mxsasha Mostly I propose we start later on both days :-D. Probably something like
Direct link to the current status of the schedule. |
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. |
@ericholscher do we want to switch to 5 min Q&A + 10 min break, keeping the spacing the same? |
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. |
Sponsor intros after lunch or before lunch? @ericholscher @katiejano I think after right? |
In Portland, sponsor intros were scheduled before the final coffee break
before lunch on Monday.
I will have time later today to add the schedule to the Master. I'll go off
of this one and let you know if I there are any edits.
…On Thu, Aug 7, 2025 at 4:26 AM Sam ***@***.***> wrote:
*plaindocs* left a comment (writethedocs/www#2399)
<#2399 (comment)>
Sponsor intros after lunch or before lunch? @ericholscher
<https://github.com/ericholscher> @katiejano
<https://github.com/katiejano> I think after right?
—
Reply to this email directly, view it on GitHub
<#2399 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BET7XOPJL3Z2S42ABD4GRAL3MMZX5AVCNFSM6AAAAACBVQXBIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNRTGY3TIOJWHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Right, I'm asking what we want. |
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. |
How about after the lightning talks? |
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. |
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. |
Yep, then I think we're all in agreement, after coffee break on Monday morning. |
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. |
@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. |
Revisiting this, lets see if we can wrap it up. I think EU folks are gonna find doors much earlier than 8:30 a bit much. Not that they have to show up then of course, but not much point if they don't. So doors 80:30, WW at 9:00 and intro at 09:30? on Monday |
-With having everyone check in Monday morning it's going to be a huge rush with only one hour. Speakers will also be arriving for tech check so I'd like to keep doors at 8 even if it's just a handful of people that check in then.
Other than that looks good. I'll confirm the master schedule is reflective of this as well. |
I fixed up the feedback I had, looks ready to go to me. I added the social to the social events page, and included that as a link as well. |
Thanks @ericholscher . I've got one potential speaker switch, but I don't think it needs to block publication. |
Thanks for updating. |
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/