[WIP] Berlin schedule work #2399
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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/