[From nobody Sat Mar 13 18:14:25 2010 Return-path: <pycon@python.org> Envelope-to: tismer@stackless.com Received: from rampart.timecastle.net ([192.67.63.145]) by centera.de with esmtp (Exim 3.35 #1 (Debian)) id 1GpX8e-0000sw-00 for <tismer@stackless.com>; Wed, 29 Nov 2006 22:38:45 +0100 Received: from localhost (localhost [127.0.0.1]) by rampart.timecastle.net (Postfix) with SMTP id 0C8052CFED for <tismer@stackless.com>; Wed, 29 Nov 2006 18:01:39 -0600 (CST) Received: from rampart.timecastle.net (localhost [127.0.0.1]) by rampart.timecastle.net (Postfix) with ESMTP id E06832D26E for <tismer@stackless.com>; Tue, 28 Nov 2006 21:20:26 -0600 (CST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: PyCon2007 proposal #85 decision From: pycon@python.org To: tismer@stackless.com Date: Wed, 29 Nov 2006 03:20:26 GMT Message-Id: <20061129032026.E06832D26E@rampart.timecastle.net> X-DSPAM-Result: Innocent X-DSPAM-Processed: Wed Nov 29 18:01:38 2006 X-DSPAM-Confidence: 0.9899 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 577,456e1f62108811784210004 X-DSPAM-Factors: 27, Received*(localhost+[127.0.0.1]), 0.01000, Content-Type*charset="us, 0.01000, e, 0.01000, e, 0.01000, participating+in, 0.01000, Received*stackless.com>, 0.01000, of, 0.01000, of, 0.01000, Received*ESMTP, 0.01000, jeff, 0.01000, Received*Nov, 0.01000, received, 0.01000, received, 0.01000, Date*GMT, 0.01000, received+this, 0.01000, received+this, 0.01000, 2007+If, 0.01000, mail, 0.01000, mail, 0.01000, we, 0.01000, we, 0.01000, error, 0.01000, because, 0.01000, because, 0.01000, To*tismer, 0.01000, Content-Type*text/plain+charset="us, 0.01000, Rush, 0.01000 Mr. Christian Tismer, Regarding PyCon proposal: 85. The Essentials of Stackless Python, < http://us.pycon.org/apps07/proposals/85/ > We are pleased to inform you that your proposal has been accepted for inclusion in the conference program. We will be contacting you further to have you confirm deadlines and give us more information relating to your presentation. For tips on writing your slides and making your presentation, please consult http://us.pycon.org/TX2007/SpeakerNotes. This is a Wiki page, so you can add your own suggestions and questions to the page. Please remember that your presentation will be published on the web. For the convenience of attendees who may reference your talk in the archives, please provide us with your final slides no later than one week before the conference (February 15th). We prefer materials in HTML or reST. If you use PowerPoint, please also provide a PDF or HTML version of your slides. You can also provide the original format if you choose. Your materials will be made available from the conference web site, but you will retain the copyright. To increase the usefulness of your presentation, we suggest (but do not require) that you place your materials under a Creative Commons license. See http://creativecommons.org/learn/licenses/ for more information. The Program Committee reviews are listed below, and are visible to authors on the pycon web site. We look forward to seeing you at PyCon 2007. Sincerely, Nicholas Bastin <nick.bastin@gmail.com>, Program Chair, PyCon 2007 Andrew Kuchling <amk@amk.ca>, Co-chair, PyCon 2007 Jeff Rush <jeff@taupro.com>, Co-chair, PyCon 2007 -------------------------------------------------------------------------------- Reviewer #16: +0 Talk seems interesting, although without more outlined in terms of what would be covered I can't give it a +1. ................................................................................ Reviewer #3: +0 Would fit nicely into a Python Implementation track. Paring down the Stackless concepts to their basics is probably useful for Python implementors on other platforms such as Parrot. ................................................................................ Reviewer #32: +0 The proposal doesn't actually leave much open regarding what attendees will learn from the talk that they haven't learned from the abstract. ................................................................................ Reviewer #146: -1 #76 seems like a stronger proposal, and I don't think we need two Stackless talks. ................................................................................ Reviewer #1: +1 This talk is relevant to the stackless community because Christian is the project leader and the talk is basically a "State of Stackless" talk that he gives each year - what is new since last year, what is cool about the architecture. It will be a very tech-detailed talk. The other stackless talk addresses a different audience, in that it seeks to communicate the benefit of -using- stackless versus this talk about internals and what's new. No real overlap. -------------------------------------------------------------------------------- You have received this e-mail because you are participating in PyCon TX 2007. If you feel you have received this e-mail in error, please contact: Jeff Rush at jeff@taupro.com ]