How to get a PyCon talk accepted...

So, deep in my second year on the PyCon Program Committee, I've got a few morsels of wisdom I'd like to share with anyone who happens to come across this posting and is thinking about submitting a proposal for a PyCon talk:

For starters, read the instructions at http://us.pycon.org/2009/conference/proposals/ (update as the years change) and really, do your best to follow them.  The biggest two points that seem to be ignored are: 

1. The description for the reviewers should be a fairly complete outline.   We like bullet points and organization of topics because it makes it clear that you've thought out the flow of your talk.  
    
2. Along with that outline, we'd like to see timing notes (i.e. how long will each section of that outline take to present) -- this tells us how you plan on using your time and it clues us in to what your focus is going to be more than a basic outline would.
   

Next, if your main point is to present your module or new app built with/for Python, help us help you:

If you've created this module or application/widget/whatever, you clearly saw a need for it. Therefore, instead of just blatantly pitching your widget, build your talk around explaining that need -- context and education is much more interesting for most topics and, if you do it right, you sell your module without actually doing much selling.  Throw in a brief intro to what you've made at the end and make yourself available after the talk.  

By framing the context, you'll do wonders for your module's popularity -- or at least convince some percentage of people that what you're doing is relevant and interesting.  Moreover, talking about the problem and context does a lot more to educate the attendees and that's big for the Python community at large.  The best part?  Everyone will feel like they've gotten something out of it rather than just feeling like they got a sales pitch.