A short description of the talk. What is it about? Is it about a module? Include a relevant link to the module. If it's a short demo; link to the relevant code on github or bitbucket.
Your aim is to get your audience interested in the topic, while being brief. Shoot for 1-3 sentences that describe what the value of your talk will be.
Lightning talks should be 5-10 minutes long, and slides are optional but encouraged.
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.
To submit your talk, fork this repository and clone it. Copy this template into your desired talk date's directory as lightning-<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
"Lightning talk proposal". Feel free to ping the organizers in #pdxnode 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 lightning talk will only be considered for the next meetup if it's submitted at least three days 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? Do they give a lot of talks, or is this their first time? Emphasis should be given to newbies who have attended at least one meetup (so you know they understand the format).
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.
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.
After the talk, feel free to edit their talk file to include links to videos, photos, slides, or other relevant links.