Showing posts with label PyCon. Show all posts
Showing posts with label PyCon. Show all posts
2011-01-24
PyCon 2011 early bird registration ends tomorrow!
If you have been putting off registering for PyCon, your time is running out to get the early bird rate as it ends January 25th! As replies on this Buzz from Jesse Noller point out, registration will break the 1000 mark very soon, meaning that 2/3 of capacity for the conference is basically already gone. As for tutorials, one is full, two more have less than five seats, and three are quickly approaching capacity. So it is not just the conference that is filling up quickly.
2011-01-21
PyCon stuff & PSF core grant, day 10
I am going to start this post with me pimping PyCon 2011. To start, early-bird registration is on until January 25th, so make sure to register ASAP. I would not procrastinate as attendance is capped at 1,500 and there are already about 50% more registrations now than there were last year when attendance hit 1,200. There is absolutely no reason to think we will not hit the cap this year and have to turn people away because they did not register soon enough.
Also don't forget to register for any tutorials you want to attend now rather than later. The most popular ones are already either full or practically there and this always leads to a cascading effect where other tutorials continue to fill up. So once again, don't procrastinate and register ASAP for tutorials.
As usual, there are some new things being tried out at PyCon this year. The latest one to be announced is Startup Row. Basically a bunch of startups are going to be highlighting there use of Python. Should be interesting as startups typically push Python pretty hard and end up developing very cool technology stacks.
And finally, a tradition amongst Python bloggers who attend PyCon is to list the five talks you are looking forward to the most. As usual that's a bloody hard list to make; I started with 30 tabs filled with talks I want to attend! But here are five I do plan to attend:
Now that I have raved about PyCon, I can talk about what the heck I did yesterday for the PSF.
After the usual fixes I went through and cleaned up the Misc directory. There was outdated stuff in there along with files that belonged more in the devguide than there; previously there just wasn't a good place to put stuff like a README on how to get Emacs set up. So I went through and pruned the directory down.
While I have been working on the devguide I had a copy of the dev FAQ that I was chopping up to keep track of what I needed to cover. Some people were worried I was going to cut out all of the questions from the FAQ concerning svn or SSH; people liked that I had bothered to answer common tool questions there over the years so that they didn't have to try to search for a solution. So I stripped out anything that would be repetitive so its more of a tools FAQ.
Because I am in the home stretch I dropped some todo items and them into issues. They revolve around creating some code which can lead to tasks for people to help with in the future.
I also went through the old dev docs and made sure I was not about to lose any critical links.
Also don't forget to register for any tutorials you want to attend now rather than later. The most popular ones are already either full or practically there and this always leads to a cascading effect where other tutorials continue to fill up. So once again, don't procrastinate and register ASAP for tutorials.
As usual, there are some new things being tried out at PyCon this year. The latest one to be announced is Startup Row. Basically a bunch of startups are going to be highlighting there use of Python. Should be interesting as startups typically push Python pretty hard and end up developing very cool technology stacks.
And finally, a tradition amongst Python bloggers who attend PyCon is to list the five talks you are looking forward to the most. As usual that's a bloody hard list to make; I started with 30 tabs filled with talks I want to attend! But here are five I do plan to attend:
- Through the Side Channel: Timing and Implementation Attacks in Python
- Packaging, from Distutils to Distutils2
- Using Python 3 to Build a Cloud Computing Service for my Superboard II
- Writing great documentation
- Why is Python slow and how PyPy can help?
There is also the Python VMs panel that I organized, but I figured I can't list that as a talk I want to attend since that seems a bit presumptuous. =)
In case my enthusiasm for PyCon in general and this year in particular is not coming through my prose, I'm excited! I have been attending PyCon since its founding in 2003 and have always had such a fantastic time that I leave the conference looking forward to the next one.
Now that I have raved about PyCon, I can talk about what the heck I did yesterday for the PSF.
After the usual fixes I went through and cleaned up the Misc directory. There was outdated stuff in there along with files that belonged more in the devguide than there; previously there just wasn't a good place to put stuff like a README on how to get Emacs set up. So I went through and pruned the directory down.
While I have been working on the devguide I had a copy of the dev FAQ that I was chopping up to keep track of what I needed to cover. Some people were worried I was going to cut out all of the questions from the FAQ concerning svn or SSH; people liked that I had bothered to answer common tool questions there over the years so that they didn't have to try to search for a solution. So I stripped out anything that would be repetitive so its more of a tools FAQ.
Because I am in the home stretch I dropped some todo items and them into issues. They revolve around creating some code which can lead to tasks for people to help with in the future.
I also went through the old dev docs and made sure I was not about to lose any critical links.
2010-09-23
Call for proposals out for PyCon 2011
Jesse Noller announced that the call for proposals (CFP) went out today for PyCon 2011. Due date is November 1.
I was actually thinking of missing PyCon 2011 as my PSF grant would end before PyCon and I was planning on starting my job at Google then (if this is the first you are hearing of either fact, don't be shocked as I have not blogged about either yet; expect more details when either event approaches). But I was told that my life depended on my attending, so I am currently planning on attending the conference.
That means I will try to give a talk as I (almost) always do. Any requests? Last year I gave a talk on custom importers which is already outdated thanks to what I have set up for Python 3.2. PyCon 2009 was my "how Python is developed, you should help" talk. PyCon 2008 was the last time I gave my import talk (I gave it at EuroPython this year, but obviously that's a different audience). In other words I can talk about anything but importlib itself. If you have an opinion on what you would like to have me talk about, just leave a comment or email me.
I was actually thinking of missing PyCon 2011 as my PSF grant would end before PyCon and I was planning on starting my job at Google then (if this is the first you are hearing of either fact, don't be shocked as I have not blogged about either yet; expect more details when either event approaches). But I was told that my life depended on my attending, so I am currently planning on attending the conference.
That means I will try to give a talk as I (almost) always do. Any requests? Last year I gave a talk on custom importers which is already outdated thanks to what I have set up for Python 3.2. PyCon 2009 was my "how Python is developed, you should help" talk. PyCon 2008 was the last time I gave my import talk (I gave it at EuroPython this year, but obviously that's a different audience). In other words I can talk about anything but importlib itself. If you have an opinion on what you would like to have me talk about, just leave a comment or email me.
2010-02-24
PyCOn 2010 reflections
[edit: forgot Brett Slatkin's and Holger Krekel's talks]
Once again PyCon was fabulous. As usual I spent very little time actually in talks, instead spending it what is known as the "hallway track". But of the talks I did see, my favorites were Holger Krekel's talk on the various Python interpreters, Collin Winter's Unladen Swalllow talk, David Beazley's GIL talk, C. Titus Brown's continuous integration talk (which if you want to here Titus take the piss out of Jesse Noller and I listen around 28:44), and Brett Slatkin's PubSubHubbub talk (video is not up yet). And of course there is my talk on importers.
The meme for PyCon 2010? Probably the testing goat.
Unfortunately I couldn't stick around for the sprints, but I still had a great time. Hopefully next year I will be done with my degree and employed by someone who will fund my attendance and let me stick around for the sprints as it felt really odd not sticking around.
Once again PyCon was fabulous. As usual I spent very little time actually in talks, instead spending it what is known as the "hallway track". But of the talks I did see, my favorites were Holger Krekel's talk on the various Python interpreters, Collin Winter's Unladen Swalllow talk, David Beazley's GIL talk, C. Titus Brown's continuous integration talk (which if you want to here Titus take the piss out of Jesse Noller and I listen around 28:44), and Brett Slatkin's PubSubHubbub talk (video is not up yet). And of course there is my talk on importers.
The meme for PyCon 2010? Probably the testing goat.
Unfortunately I couldn't stick around for the sprints, but I still had a great time. Hopefully next year I will be done with my degree and employed by someone who will fund my attendance and let me stick around for the sprints as it felt really odd not sticking around.
2009-12-30
Reminder: PyCon 2010 early bird registration ends January 6!
So people don't forget to register for the early bird rate for PyCon, it closes January 6. Below is the email sent to python-dev by Van Lindberg, PyCon chair for 2010:
Do you have a year-end hole in your training budget? Or will the
improved economy let you finally attend a work conference? Come to sunny
and warm Atlanta in February for PyCon 2010. Early bird registration
ends on January 6.
Register: https://us.pycon.org/2010/register/
See the talks: http://us.pycon.org/2010/conference/talks/
Get trained at a tutorial: http://us.pycon.org/2010/tutorials/
Also see the five (or more!) talks that people can't miss at PyCon:
PyOraGeek: PyCon pre-favorites
<http://catherinedevlin.blogspot.com/2009/11/pycon- pre-favorites.html>
Pyright: PyCon pre-favorites, the Carl T. edition:
<http://pyright.blogspot.com/2009/11/pycon-2010-pre- favorites-carl-t-edition.html>
Aftermarket Pipes: Five Pycon 2010 Talks I Need to See:
<http://apipes.blogspot.com/2009/12/five-pycon-2010-talks- i-need-to-see.html>
Jessenoller.com: PyCon 2010: Talks I want to see:
<http://jessenoller.com/2009/12/06/pycon-2010-talks-i-want- to-see-keynotes-registration- open/>
The Third Bit: Five PyCon Talks I Want To See:
<http://pyre.third-bit.com/blog/archives/3364.html>
See you at PyCon!
Register: https://us.pycon.org/2010/register/
2009-12-04
PyCon 2010 early-bird registration is open!
In case you have not heard yet, PyCon 2010 early-bird registration is now open and will end on January 6.
2009-11-04
PyCon talk decisions have been made
[edit: nixed a paragraph by request]
[edit: link to accepted talks and thank Doug]
I want to say three things in this post. One is that the PyCon program committee has finished making there decisions of which 95 talks out of the 179 submissions we received. I should also admit that my talk (#9 in the list) was accepted although I actually missed the part of PC meetings where it was so I didn't officially find out until everyone else did.
Second, I wanted to publicly thank Jesse Noller and the other members of the pycon-pc for their hard work (with special honorable mention to Doug Napoleone for pycon-tech, the software that keeps PyCon running). We had a record number of submissions with an average of only 10 people in IRC to go over them during the culling process. It was grueling, but people stuck in there and helped make it happen (and I admit I did not participate as much as I would have liked due to a conference paper submission I had).
Third, I want to address the negativity that has been popping up about the decisions we had to make (some of which led to hate mail sent personally to Jesse which is completely uncalled for). There seems to be two themes that have popped up as to why people are upset over there rejection.
One is their talk received all positive reviews but was still rejected. Sorry, but that's called time restriction. We honestly had more talks with all positive reviews than we had slots. And just because your talk didn't receive any negative reviews does not mean that it fired anyone up enough to want to stand up for it. We use a Champion voting system where a talk only gets considered if a reviewer is willing to take a stand saying they will fight for the talk to be included. If a talk has a lot of people standing up for it then it will get in without question, but it takes A LOT of people for that to happen (like four or more, and there were not that many talks like that). Otherwise we have to discuss the talk. And if the people fighting for the talk can't convince the PC (or don't make the IRC meeting which is just life since we can't infinitely postpone to make everyone's schedule) then the talk is let go. So if your talk received all positive reviews and you are wondering what it was rejected in the end, it means it unfortunately didn't attract a champion that was either to argue for it in a way to win over the other PC members in IRC.
The second theme has been how the talks are not anonymous to reviewers. This is a conscious decision that we have made from years of experience where it matters whether we know upfront whether someone is a good speaker. We tried anonymous reviewing one year and it turned out badly. PyCon does not have a proceedings like academic computer science conferences where if someone can't present you still have the work in paper form. At PyCon if you are a good speaker that counts for a lot as speaking is how you share your knowledge. And if people think you are not a great speaker that usually means someone won't champion your talk, not that you will get a -0 or -1 (if that does happen it is usually a sign of a bad review, but once again we were short on people and some bad reviews slipped through).
[edit: link to accepted talks and thank Doug]
I want to say three things in this post. One is that the PyCon program committee has finished making there decisions of which 95 talks out of the 179 submissions we received. I should also admit that my talk (#9 in the list) was accepted although I actually missed the part of PC meetings where it was so I didn't officially find out until everyone else did.
Second, I wanted to publicly thank Jesse Noller and the other members of the pycon-pc for their hard work (with special honorable mention to Doug Napoleone for pycon-tech, the software that keeps PyCon running). We had a record number of submissions with an average of only 10 people in IRC to go over them during the culling process. It was grueling, but people stuck in there and helped make it happen (and I admit I did not participate as much as I would have liked due to a conference paper submission I had).
Third, I want to address the negativity that has been popping up about the decisions we had to make (some of which led to hate mail sent personally to Jesse which is completely uncalled for). There seems to be two themes that have popped up as to why people are upset over there rejection.
One is their talk received all positive reviews but was still rejected. Sorry, but that's called time restriction. We honestly had more talks with all positive reviews than we had slots. And just because your talk didn't receive any negative reviews does not mean that it fired anyone up enough to want to stand up for it. We use a Champion voting system where a talk only gets considered if a reviewer is willing to take a stand saying they will fight for the talk to be included. If a talk has a lot of people standing up for it then it will get in without question, but it takes A LOT of people for that to happen (like four or more, and there were not that many talks like that). Otherwise we have to discuss the talk. And if the people fighting for the talk can't convince the PC (or don't make the IRC meeting which is just life since we can't infinitely postpone to make everyone's schedule) then the talk is let go. So if your talk received all positive reviews and you are wondering what it was rejected in the end, it means it unfortunately didn't attract a champion that was either to argue for it in a way to win over the other PC members in IRC.
The second theme has been how the talks are not anonymous to reviewers. This is a conscious decision that we have made from years of experience where it matters whether we know upfront whether someone is a good speaker. We tried anonymous reviewing one year and it turned out badly. PyCon does not have a proceedings like academic computer science conferences where if someone can't present you still have the work in paper form. At PyCon if you are a good speaker that counts for a lot as speaking is how you share your knowledge. And if people think you are not a great speaker that usually means someone won't champion your talk, not that you will get a -0 or -1 (if that does happen it is usually a sign of a bad review, but once again we were short on people and some bad reviews slipped through).
2009-10-20
Submit a poster for PyCon 2010
The PyCon organizers are trying something new for PyCon 2010: posters. Basically there is a plenary session where people have posters about something and they stand there talking to whomever comes by (if you have been in academia you know what these can be like). In my time doing posters at academic conferences I have found that at the larger conferences a poster can be worth your time. You end up with enough people coming by talking to you that you get valuable feedback and contacts. Plus a poster is a lot less stressful to do compared to a full talk and allows for more detail than a lightning talk.
So if you have something you want to say that can be put on a poster and want some feedback on it or simply share with the PyCon attendees, please consider making a poster.
So if you have something you want to say that can be put on a poster and want some feedback on it or simply share with the PyCon attendees, please consider making a poster.
2009-09-16
PyCon 2010 talk proposals due in two weeks
Just a reminder to folks out there that the due date for submitting a talk to PyCon 2010 is two weeks away!
2009-09-02
Less than a month to submit a PyCon 2010 talk
PyCon talk proposals are due October 1, which is less than a month (four weeks) away. I have already submitted a talk on custom importers and using importlib to write your own.
2009-08-13
PyCon 2010 Call for Proposals
Below is the CFP for PyCon 2010 which just went out. I am currently leaning towards doing a talk on custom importers and importlib myself (unless people want to hear something else from me; leave a comment if you have an opinion).
PyCon is your platform for getting the word out and teaching something new to hundreds of people, face to face.
Previous PyCon conferences have had a broad range of presentations, from reports on academic and commercial projects, tutorials on a broad range of subjects and case studies. All conference speakers are volunteers and come from a myriad of backgrounds. Some are new speakers, some are old speakers. Everyone is welcome so bring your passion and your code! We're looking to you to help us top the previous years of success PyCon has had.
PyCon 2010 is looking for proposals to fill the formal presentation tracks. The PyCon conference days will be February 19-22, 2010 in Atlanta, Georgia, preceded by the tutorial days (February 17-18), and followed by four days of development sprints (February 22-25).
Online proposal submission is open now! Proposals will be accepted through October 1st, with acceptance notifications coming out on November 15th. For the detailed call for proposals, please see: http://us.pycon.org/2010/conference/proposals.
For videos of talks from previous years - check out: http://pycon.blip.tv.
We look forward to seeing you in Atlanta!
Call for proposals -- PyCon 2010
Due date: October 1st, 2009
Want to showcase your skills as a Python Hacker? Want to have hundreds of people see your talk on the subject of your choice? Have some hot button issue you think the community needs to address, or have some package, code or project you simply love talking about? Want to launch your master plan to take over the world with python?PyCon is your platform for getting the word out and teaching something new to hundreds of people, face to face.
Previous PyCon conferences have had a broad range of presentations, from reports on academic and commercial projects, tutorials on a broad range of subjects and case studies. All conference speakers are volunteers and come from a myriad of backgrounds. Some are new speakers, some are old speakers. Everyone is welcome so bring your passion and your code! We're looking to you to help us top the previous years of success PyCon has had.
PyCon 2010 is looking for proposals to fill the formal presentation tracks. The PyCon conference days will be February 19-22, 2010 in Atlanta, Georgia, preceded by the tutorial days (February 17-18), and followed by four days of development sprints (February 22-25).
Online proposal submission is open now! Proposals will be accepted through October 1st, with acceptance notifications coming out on November 15th. For the detailed call for proposals, please see: http://us.pycon.org/2010/conference/proposals.
For videos of talks from previous years - check out: http://pycon.blip.tv.
We look forward to seeing you in Atlanta!
2009-08-01
PyCon 2010 site is live
The official site for PyCon 2010 is now up and running. For those of you who don't know, PyCon 2010 will be in Atlanta, Georgia in mid/late February.
As I have said before, PyCon 2009 was the best PyCon ever, and I have been to every single one of them. There is no reason why 2010 should not be as good as 2009.
2009-03-15
Google Moderator pages for PyCon VM panel
I organized a VM panel at PyCon this year where a representative from each of the major VMs (CPython, Jython, IronPython, and PyPy) will be in one room to answer your various questions. To help get questions from people who cannot attend along with making our esteem MC's job easier, Jacob (who is the moderator) and I have set up a Google Moderator page for the panel to propose qauestions.
Please propose questions or vote questions up and down so that Jacob can come with a battery of questions for the panel to fill in lulls during the Q&A. And I think all talks are being recorded this year so the panel should eventually end up online.
Oh, and if you are not attending PyCon, you still have a chance to register and come!
Please propose questions or vote questions up and down so that Jacob can come with a battery of questions for the panel to fill in lulls during the Q&A. And I think all talks are being recorded this year so the panel should eventually end up online.
Oh, and if you are not attending PyCon, you still have a chance to register and come!
2009-02-19
Three days left for PyCon early bird registration!
Just a reminder that PyCon early bird registration ends in three days! There are 439 people publicly registered at the moment which, last time I heard, puts us on track to be over 1,000 attendees again! Looks like the economy is not going to suppress attendance at PyCon which is great!
Actually, this PyCon will probably have the highest number of core developers in attendance than any other previous PyCon thanks to the language summit. That should make the conference interesting to me just from the standpoint of the hallways conversations that will most likely spring up.
Actually, this PyCon will probably have the highest number of core developers in attendance than any other previous PyCon thanks to the language summit. That should make the conference interesting to me just from the standpoint of the hallways conversations that will most likely spring up.
2009-02-05
Invited speakers at PyCon announced
When the list of accepted talks for PyCon 2009 was released, it wasn't the whole story in terms of scheduled content. This year the program committee decided to do something different and have invited talks. Now, short of the keynotes which have not been announced, people have a very clear picture of the great content that is set to be shown at PyCon this year.
[Full disclosure: I am on the PyCon program committee as well as an invited speaker, although I didn't know I was invited until I got the invitation =) ]
[Full disclosure: I am on the PyCon program committee as well as an invited speaker, although I didn't know I was invited until I got the invitation =) ]
2008-12-17
My PyCon panel has been accepted
My talk for PyCon 2009 on how python-dev is developed was an invited talk, so there was no anticipation on that front. Hoping to keep the talk entertaining and light while convincing everyone in the audience to help in the development of Python. How Python is developed is not complex, just very organic and time-consuming. But I will cover what *should* be the typical workflow. =)
What was explicitly accepted by the program committee is my panel on Python VMs (disclosure: I am on the program committee, but I was not allowed to vote on my own proposal nor know its status). The panel is going to have Dino Viehland of IronPython, Holger Krekel of PyPy, Jim Baker of Jython, and myself for CPython. Jacob Kaplan-Moss of Django will be the moderator.
As always the conference will be fun! Already looking forward to some talks, such as Jese Noller's multiprocessing talks. And if I manage to get importlib far enough along maybe I will hold an Open Space on imports to see what people want in terms of support from the library.
What was explicitly accepted by the program committee is my panel on Python VMs (disclosure: I am on the program committee, but I was not allowed to vote on my own proposal nor know its status). The panel is going to have Dino Viehland of IronPython, Holger Krekel of PyPy, Jim Baker of Jython, and myself for CPython. Jacob Kaplan-Moss of Django will be the moderator.
As always the conference will be fun! Already looking forward to some talks, such as Jese Noller's multiprocessing talks. And if I manage to get importlib far enough along maybe I will hold an Open Space on imports to see what people want in terms of support from the library.
2008-10-22
PyCon proposal deadline in less than two weeks
Just a reminder to people who are planning to submit a proposal to PyCon: tutorials are due Oct 31 and talks are due Nov 3.
2008-10-13
REMINDER: PyCon tutorial and talk proposals due in less than a month
Just a friendly reminder to people that PyCon tutorial proposals are due on Oct 31 (a little over 2 weeks away) and talks are due Nov 3 (three weeks away). Part of what makes PyCon so great are the talks, so please consider contributing to that by proposing a talk!
And as I say year after year, PyCon is tons of fun so even if you don't feel up for giving a talk or tutorial, I highly suggest attending.
And as I say year after year, PyCon is tons of fun so even if you don't feel up for giving a talk or tutorial, I highly suggest attending.
2008-10-09
My invited talk at PyCon 2009 and a poll question for the community
[edit: I should my left from my right by now, but apparently I didn't when I first posted]
So it turns out some people think I am a decent speaker; I was made an invited speaker for PyCon 2009. That means my proposed talk on how Python is developed has already been accepted. =)
That leaves choosing a panel to organize (yes, I am a glutton for punishment when it comes to PyCon). I was originally planning on organizing a panel of core developers much like I did at PyCon 2007. But some rumblings from various people have reached me that suggest people might actually prefer a panel on Python VMs.
Since I don't know many "typical" users of Python, I figured I would toss this out to the community to let me know what panel might be preferred. If you look in the right-hand column of my blog you will notice a poll question asking whether you would prefer a python-dev or Python VM panel. If you have a preference, please vote. I won't promise that the winning one will be what I try to plan, but I will take it under consideration.
So it turns out some people think I am a decent speaker; I was made an invited speaker for PyCon 2009. That means my proposed talk on how Python is developed has already been accepted. =)
That leaves choosing a panel to organize (yes, I am a glutton for punishment when it comes to PyCon). I was originally planning on organizing a panel of core developers much like I did at PyCon 2007. But some rumblings from various people have reached me that suggest people might actually prefer a panel on Python VMs.
Since I don't know many "typical" users of Python, I figured I would toss this out to the community to let me know what panel might be preferred. If you look in the right-hand column of my blog you will notice a poll question asking whether you would prefer a python-dev or Python VM panel. If you have a preference, please vote. I won't promise that the winning one will be what I try to plan, but I will take it under consideration.
2008-09-26
PyCon 2009 CFP is out
The Call For Papers for PyCon 2009 is now up. Due date is November 3.
This year I am thinking of doing my talk on how Python is developed (last given as a talk back in DC) and perhaps another python-dev panel (last done in 2007).
This year I am thinking of doing my talk on how Python is developed (last given as a talk back in DC) and perhaps another python-dev panel (last done in 2007).
Subscribe to:
Posts (Atom)