TimeShift VS Back In Time

The previous developer of timeshift—Tony George (GitHub) — has been the developer since 2017 (based on GitHub version history), and has recently handed off development to the Linux Mint team.

I use both timeshift & duplicity

Don't believe me or u/acejavelin69 - read what the developer has to say about user data and why it is disabled by default. https://github.com/teejee2008/timeshift

Version v22.06.6 Latest

The original dev used ubuntu and only wanted to support the default ubuntu layout: https://github.com/teejee2008/timeshift/issues/821

What system backup software can you recommend? In the past on Ubuntu I tested Timeshift, and it looks really cool. But the "main problem" is thing, that some options not work in Fedora: https://github.com/teejee2008/timeshift, specifically BTRFS. What does it mean, this is a problem?

- [Timeshift](https://github.com/teejee2008/timeshift) or [Deja Dup](https://wiki.gnome.org/Apps/DejaDup) and back-up everything.

What I tried is to add "exclude" : [ "+ /home/user1/**", "+ /root/**", "+ /home/user2/**", ], to /etc/timeshift.json as per this post but the files within those folders still aren't included in the backup.

Releases · teejee2008/timeshift Was fixed. Get PPA from that repo to have the latest release.

Are you sure you need a full on virtual machine, rather than a system snapshotting tool like Snapper or Timeshift?

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.

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.