I have 2 accepted talks at Pycon, that is great. I would like to say that the Pycon review system is awesome because you can see what the reviewers have said, and understand why your talk was accepted or declined.
I was a bit frustrated that my Atomisator talk was declined, but I think it makes sense : this is a new tool, and beside my user group and a few people, it is not really used yet.
One reviewer said that it had to be picked, and another one answered :
I agree that PyCon should not restrict itself to well-known projects, but it should definitely restrict itself to projects that are (a) in production use, (b) under active development, and (c) likely to still be so in a year. There are so many projects meeting these criteria that for me, the bar is very high indeed to spend a talk slot on one that does not.
Ok, fair enough : I will present this talk at Pycon 2010 and they won’t have any argument to decline it 
The talks that made it:
- How AlterWay releases web applications using zc.buildout
- On the importance of PyPI in delivering and building Python softwares – mirroring, fail-over and third-party package indexes
I will get into greater details later on.
2 talks is already really hard… more than that and you’d be totally buried. So consider it a good thing you didn’t get any more accepted
Comment by Ian Bicking — December 17, 2008 @ 3:32 am |
Congratulations on getting the two talks accepted. Could you put together a simple tutorial on extending / contributing to Atomisator? Ie. what does a plugin (reader / enhancer / output) need to implement to work well within the framework? I have written something a bit similar to Atomisator, and would rather switch to using it than maintain my own stuff. There’s a few new plugins such as email retrieval & processing, plone output etc. that I could contribute.
I did not see any common base classes or interfaces for Atomisator plugins – from what I could see from a quick look, things revolve around an “entry” that’s a dictionary containing “link”, “summary” & “title”? I would suggest making things a bit more generic by making an entry a class (or a tuple) that contains two items: “content” and a dictionary containing free-form key-value pairs.
Petri
Comment by Petri Savolainen — December 17, 2008 @ 9:40 am |
@Ian : yes that’s true
@Petri: Thanks !
This is great news ! I’ll write a small documentation then asap, so you can contribute if you wish.
in a few words:
- plugins can be any class, that is registered as a setuptools entry point. For instance :
http://atomisator.ziade.org/browser/packages/atomisator.enhancers/setup.py
see the entry_points for the enhancers at the beginning.
Now for the entry, historically it was only for rss feeds so I totally agree on your analysis.
Comment by Tarek Ziadé — December 17, 2008 @ 11:27 am |
Congrats Tarek. Btw, where you do you see the votings and the ratings?
My tutorial proposal has been accepted and I am curious to know how many +1s,-1s and 0s it obtained. I would be presented a tutorial on “A Tour of Python Standard Library”.
Btw, I just a the user of ignore flag in shutil.copytree. I feel its a great addition, in replacing a 4-5 lines to code which we used to do previously with a single line. I saw that change was added by you. Thanks!
Comment by Senthil — January 1, 2009 @ 8:08 am |
@Senthil, thanks ! Fo rthe reviews, you need to log in the site, and you will see them in “my proposals” (as long as the tutorial review process works the same way)
For copytree: you are welcome ! this small change slims a lot the amount of code needed when you work a lot with the file system (which I do)
Comment by Tarek Ziadé — January 4, 2009 @ 7:55 pm |