<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 19 Jun 2013 21:56:23 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Joe Devon's Blog: How to get your talk accepted, experiences on the advisory board of Semtech & Zend]]></title>
      <guid>http://www.phpdeveloper.org/news/16831</guid>
      <link>http://www.phpdeveloper.org/news/16831</link>
      <description><![CDATA[<p>
As a result of the <a href="http://zendcon.com">ZendCon</a> advisory board for this year's event, <i>Joe Devon</i> has <a href="http://mysqltalk.wordpress.com/2011/09/07/how-to-get-your-talk-accepted-experiences-of-being-on-the-advisory-board-of-semtech-zendcon/">posted a guide</a> that wants to help you get your talks accepted to conferences in the future (both PHP-related and not).
</p>
<blockquote>
For those who don't know what an advisory board is, conference organizers get loads of proposals and need help deciding who should speak. So they ask others in the industry to provide some feedback. It was quite a learning experience.
</blockquote>
<p>
He talks some about the "speaker backlash" that comes from being rejected, a lack of professionalism in some submittors and some basic (common sense) recommendations like:
</p>
<ul>
<li>fill out the form completely, even if you don't think it's all useful
<li>start locally and then move up. A major conference isn't the place to try out your speaking first-shot
<li>whet the board's appetite - make them want to hear more about the topic or come up with something new
<li>share your unique experience with the technology
<li>use sites like <a href="http://joind.in">Joind.in</a>, <a href="http://meetup.com">Meetup</a> and <a href="http://slideshare.com">SlideShare</a> to your advantage
</ul>]]></description>
      <pubDate>Thu, 08 Sep 2011 08:56:58 -0500</pubDate>
    </item>
  </channel>
</rss>
