A 2-5 sentence description of the talk. If you've got a long demo of a bunch of modules, or higher level topic, it should be a long-form talk. Be prepared to accept questions at the end of the talk!
Your aim is to get the audience interested in the topic, and to include any relevant material that'll pique their interest. Your talk doesn't necessarily have to be Node.js specific, we love it when people care deeply about their topic and are excited to share!
Long-form talks should be 20-30 minutes long and you should plan to have slides. Also be ready for a few minutes of questions immediately following.
Include a link to your github profile, and it'd be cool if you embedded your avatar. What do you do for a living? How do you use Node? Include your twitter handle, if applicable.
Why is this talk relevant to what you do? How did you come across this topic?
To submit your talk, fork this repository and clone it. Copy this template into your desired talk date's directory as your_talk_name.md. Then, edit it to describe your lightning talk! Commit your new file, and push it to your fork, then issue a pull request titled "Talk proposal". Feel free to ping the organizers on Twitter at @pdxnode or in #nodepdx on IRC to ensure they see your pull request. If your talk is accepted, it will get merged and the organizers will reach out to you via email.
Your talk will only be considered for the next meetup if it's submitted at least one week in advance, to allow for discussion and deliberation.
Review the talk and the discussion on the pull request before merging. Has this person given good talks in the past? Have they never given a long form talk but have given several lightning talks in the past? How have those talks been received? Emphasis should be given to folks that haven't given a talk before, but have 1-3 lightning talks under their belt.
If you decide to accept the talk, merge the pull request and email the contributor (use the email on their commit) to let them know their talk has been accepted. Plan to reach out to them 3-4 days before their talk to check on them / make sure they're prepared / ask them if they need anything else in preparation for their talk. If a speaker has to cancel, reach out first to the other talk proposals, and in the case that no one is prepared to give a talk on short notice, scheduled extra lightning talks.
After the talk, feel free to edit their talk file to include links to videos, photos, slides, or other relevant links.
If you decide not to accept the talk, but want to consider it for a future meetup, decline the pull request and comment to this effect. Be sure to get specifics from the potential speaker in re: potential meetup dates that'd they'd be able to commit to.
If the talk is unacceptable (for any of the reasons set for the in the code of conduct, or otherwise); close the pull request. Ideally, link to the relevant headers in the code of conduct, or otherwise explain your decision.