Today our guest is one of the developers of the popular (GTK)
gPodder podcast aggregator (we
have already talked a little about this program) Leonid “PhoeniX” Ponomarev.
...I understand that you consider gPodder the most convenient client :) Why?')
When I first started listening to podcasts, I naturally began to look for suitable software.
gPodder most corresponded to my expectations in how the podcast aggregator should look and behave, and there were no annoying flaws or religious considerations, as in other variants. More precisely, you will not say so much time has passed.
How popular is your development, if not a secret?To avoid misunderstanding, let's make a reservation right away -
gPodder is not my development. The author of the project is
Thomas Perl , a student from Vienna. I just take part in this project. Interestingly, our universities have an affiliate program, and Thomas and I met through his project. The popularity of such a program is difficult to judge. This is not an office suite and not a desktop environment, to be asked about in numerous preferences polls, a rather specific program, the podcast aggregator. Many people do not know what a podcast is, who knows - listens from a web page
or what happened, that is, in your favorite player (if the latter allows it). However, if we take into account the fact that simple people come to the development mailing list and ask questions, suggest improvements, write documentation, draw icons and generally begin to help in every way, the project has popularity.
What are the reasons for joining the gPodder?I lacked the support of Russian. It turned out that I first worked on one of the unsupported scripts, the code was run in and later added to the main
gPodder code base. Then fixes to support non-unicode locales ... So I learned more and more Python and learned more about
gPodder from the inside.
What problems arise when developing such a program?Development language A joke, in general, but with a bit of a joke. Although I study it in order to take part in the development of the project, I still don’t like Python as I did five years ago. There are things in it, because of which you just grab your head, causing problems in short and clear code, forcing you to write unnecessarily verbose and ugly code to solve them. Fixing one of these problems in gPodder was one of my following patches. Then the problem manifested itself in another place, I found the source in the python itself and cut, like a proud knot, a rather dirty, but effective hack. But on other machines, this problem will arise again. So you have to crush crutches caused by language imperfections.
There is a good
presentation , however, in German, dedicated to gPodder, which Thomas conducted at the recent Linuxwochen 2008 in Vienna. In it, among other things, Thomas talks about the difficulties that arise - incorrect feeds, performance, outdated packages in distributions, iPods, and other closed devices, dependencies. From myself I would add that often there are all sorts of "everyday problems" - hosting, spam on wikis and fools who, without understanding and not using plainly, write reviews like
this . Sometimes I write about news or project difficulties on my
blog .
What development tools do you use? And how is the joint development going?I always use two development tools - the Vim text editor and the interpreter / compiler of the language used. The rest - according to circumstances, salt and pepper to taste. No delights of all kinds of IDE will not cover one of their main drawbacks - the editor in them is not Vim, which means it will be inconvenient for me.
Joint development is mainly using the mailing list and bugtracker. People choose a piece of work that they can do, or realize their idea and send the patch to the list. Anyone testing. Thomas is testing, perhaps he picks up an interesting idea (as with my last patch, he added a part to support a new iPod chip, which I don’t have) and applies it to the current code base.
Once a month a week before the next release - stabilization. Only bug fixes and translation updates. No new features and new bugs;)
What parts of the project are you working on now?I usually just finish what I’m missing. Well, here are a few releases in a row complement the Russian translation.
What interesting features to expect in new versions? And how long is version 1.0 left to wait?Why wait? Download the source (especially suffering, like me, can be installed from svn) and only two words `make install`. No need to wait for the maintainer of your distribution to lay out the day before yesterday bugs in the form of a package. For my taste,
gPodder is developing too fast to be set from
distribution kit. Planned new features are described in roadmap, which can be found on the wiki.
project.
How do you feel about podcasting, do you run your podcast? What are you listening / watching?I take it purely positive (and not from the word put). A pretty good way to turn in time travel time. I do not keep my own, I have enough
blog , although I have already been invited to others. While I refuse for lack of equipment. So who knows.
I listen to the well-known
Radio T and
U , Gray's podcast "
IT Thought, " about
L-talks Linux, which I wish successful sequels, a few Ruby-themed topics. Also in gPodder there are several tapes of video from different conferences, so it’s quite comfortable to watch, although it’s not a podcast at all. This is done, for example,
here . I think to unsubscribe from the
staff and a few more uninformative. And in general, when the hands reach, I’ll post OPML with my blog subscriptions - a good way to indicate a circle of interests.
Original on Podkastim.ru