-
Notifications
You must be signed in to change notification settings - Fork 512
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
Launch Portland 2025 CFP #2241
Launch Portland 2025 CFP #2241
Conversation
This is just a draft PR to do some initial testing, but will eventually get content updates before we go live.
@plaindocs We aren't necessarily gonna ship the whole site w/ the CFP if we haven't reviewed it all, but we can always just swap the full site flag before shipping if needed. |
Co-authored-by: Sarah Moir <[email protected]>
Ah yeah, soz for coopting your PR in that case :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copy edited the mailing -- overall looks solid.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some edits and suggestions
Co-authored-by: Alicia Duncan <[email protected]> Co-authored-by: Eric Holscher <[email protected]>
Thanks for the eyes folks, I've merged all of that, with a couple of minor changes. |
1695ac5
to
3fd323d
Compare
docs/_data/portland-2025-config.yaml
Outdated
notification: "February 04, 2025" # (Mon) 8 weeks to write and prepare | ||
info_by: "April 21, 2025" # (Mon) 2 weeks before for info for emcee |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need info much before that for social media posting, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, this is reverted in the CFP page, and I'll remove from here as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also need to update the emails to go hand in hand, but that doesn't need to block this PR.
@ericholscher made some minor updates, will update the emails page separately. Wanna merge and post on Monday? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to ship.
What date do you want to announce speakers? Right now, we have CFPs closing on January 21 and February 4 to notify speakers of whether they're speaking. We'll need at least a week to get confirmation from everyone that they're still able to speak. Are you wanting to announce February 12 or 13? That's a pretty quick turnaround so I am wondering if we should move up a date earlier. |
Edits to the CFP page: Under Conference goals
Under Speaker benefits & logistics
Under Submit your proposal
|
That's for the private confirmations, the announcement can come about a week after that yeah. But we don't need to publicize that either. So no action needed. I've made the other edits, good calls there. |
This is just a draft PR to do some initial testing,
but will eventually get content updates before we go live.
📚 Documentation preview 📚: https://writethedocs-www--2241.org.readthedocs.build/