pyvideo status: April 15th, 2012

, Will Kahn-Greene | share this (mastodon)
Note: This is an old post in a blog with a lot of posts over a long span of time. The world has changed, technologies have changed, and I've changed. It's likely this is out of date, the code doesn't work, the ideas haven't aged well, or the ideas were terrible to begin with. Let me know if you think this is something that needs updating.

What is pyvideo.org

pyvideo.org is an index of Python-related videos on the Internet. For the most part, it's a collection of videos from Python-related conferences. Saw a session you liked and want to share it? It's likely you can find it, watch it, and share it with pyvideo.org.

Status

I started richard in order to build pyvideo.org. I threw it together in like 3 weeks and it had a lot of issues. Since then, I've had a lot of help from Reiner Gerecke and the project is moving along. There are a few more things I want before I consider richard to have a critical mass sufficient to do a version release, but we're pretty close. I'm pretty excited about that.

I updated pyvideo.org with the latest richard code today. I also spent some time fixing the speaker data---it's still kind of screwy. Amongst other things we had 3 Wesley Chuns! Now there is only one.

M.-A. Lemburg submitted two more conferences to get added for a grand total of three in my queue now. I upstreamed some fixes to vidscraper a couple of weeks ago. Once we land the API changes in richard, I'll be able to add new conferences much more easily. Right now I have to do each video by hand... it's kind of a drag.

Anyhow, things are going well, though the site looks the same and many of the issues are still there. You'll just have to take my word for it for now.

If you're interested in helping out, I sure could use you! Testing, documenting, fixing the layout of some of the pages, implementing new features, fixing project infrastructure---there are a lot of different kinds of things you could help out with. Even looking through the code and pointing out egregious issues---that's also very helpful and very welcome.

Issue trackers are here:

Code is here:

Want to comment? Send an email to willkg at bluesock dot org. Include the url for the blog entry in your comment so I have some context as to what you're talking about.