Back In Time VS feedparser

it is often asked by beginners how and where starting to contribute. As member of the maintenance team of Back In Time (Backup software using rsync in the back, written with Python and Qt) I would like to introduce one of our "good first issues" (#1578).

I'm member of the upstream maintenance team of Back In Time a rsync-based backup software. No one gets payed. No company behind hit. Even the maintainers and developers are volunteers.

Back In Time is a round about 15 years old backup software using rsync in the back. I'm part of the 3rd generation maintenance team there. A lot of work in investigating and fixing issues, understanding, documenting and refactoring old code.

This request is related to an Open Source project named Back In Time. Everyone there works voluntarily and unpaid.

In my own project we do it more transparent. We close if there is a good reason for it. We don't close just because no one is working on something. If there are no resources to work in it now but it seems important we keep it open until it is fixed. We do use milestones and priority labels to give the users an idea about our plans.

I'm member of the maintenance team of Back In Time a rsync-based backup software.

Most of the strings are form two past developers (the founder and the past maintainer). Since last summer we took over the project and try to clean things up. Some of the source strings just got a review from a linguist and he also mentioned about that exclamation marks. But he kind of stopped at some point because it was to much. ;)

Currently the translation is locked because of maintenance issues and an open PR offering review of original English strings.

Great and thanks. Feel free to ask further questions in the Issues section of our project or the bit-dev.python.org mailing list. Of course you can contact me directly here.

I'm interested in that topic because I'm member of the maintenance team of Back In Time, the software discussed in that video. The version in video is 0.9, today Back In Time reached 1.3.3. Also interesting is that I'm the third generation of maintainers to that project. I'm not sure but 0.9 there was the fist maintainer and founder involved only.

There is JSON Feed¹ already. One of the spec writers is behind micro.blog, which is the first place I saw it(and also one of the few places I've seen it). I don't think it is a bad idea, and it doesn't take all that long to implement it.

I have long hoped it would pick up with the JSON-ify everything crowd, just so I'd never see a non-Atom feed again. We perhaps wouldn't need sooo much of the magic that is wrapped up in packages like feedparser² to deal with all the brokeness of RSS in the wild then.

¹ https://www.jsonfeed.org/

² https://github.com/kurtmckee/feedparser

What sites did you try? Looked into RSS yet? Many sites have RSS feeds you can use with something like https://github.com/kurtmckee/feedparser nytimes.com feeds: https://www.nytimes.com/rss

feedparser

You can explore FeedParser too

feedparser is a python package receiving and parsing RSS/Atom newsfeeds. The maintainer is active but really need much more support.

Lo más sencillo que conozco para monitorizar canales de YouTube son los feeds RSS que tiene cada canal. El formato es https://www.youtube.com/feeds/videos.xml?channel_id=[CHANNEL_ID]. Si no conoces RSS, echa un vistazo en la wiki. Para leer RSSs en Python tienes feedparser (y seguramente muchas más).