I lean a little toward the change to "backup". As I work with the code I type "backup" then backspace to type "snapshot" to be consistent with the existing usage. I'm not sure that "snapshot" is really identifying it with any more clarity than the more common term, so it feels a little fussy. And, if anything, maybe "snapshot" implies something a little more particular, like a frozen-in-time capture of the filesystem, which is not what we are making. -------- Original Message -------- On 11/5/24 3:02 AM, <c.buhtz@posteo.jp> wrote:
Hello folks,
I am interested in your opinions about this.
Looking into my foggy memory it seems that I somehow asked this question before. But I couldn't find out when and where. So my apologize if this is a duplicate.
In my experience around BIT I would say that the term "Backup" is more appropriate for what we currently call "Snapshot". So I would like to change that.
- For someone not knowing BIT (e.g. potential new users and translators) the term "Backup" is clearer. - Snapshot might be understood by some people as an image of the file system. - When writing about BIT (in Issues, Forums, etc) most of the time I do use the term "backup" out of the stomach without thinking about it.
I do understand that "Snapshot" is kind of fancy and points to the timeline feature. But I would prefer to use the technical correct term "Backup" instead of a marketing term.
What do you think?
Regards, Christian _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: derek.veit@protonmail.com