Hi,
I am glad about the current initiative to keep BiT alive.
The easiest (but still helpful) thing to start with, would be to update
the documentation.
The issues on github contain a lot of information, some of which should
also be consolidated at one place, I think.
[1] refers to a FAQ page and an external (readthedocs.io) page.
I suggest to also create a page with a title like "Known problems" that
can directly be found from [1].
It could e.g. include information about
- the fact that BiT does not start on Ubuntu 22.04, together with
possible workarounds (strictly speaking, no longer a problem of BiT
itself, but of Ubuntu, but still relevant to a lot of users)
- the changed permission behaviour in newer Bit versions
- incompatibility with rsync 3.2.4
What do you think?
[1] https://github.com/bit-team/backintime/wiki
Regards,
Alex
Greeting's to you all,
it would be nice if all of you could introduce yourself. In the group
it would be useful to know each other especially the IT related skills
and expertise.
I'm Christian Buhtz from Germany in my late 30s.
My primary repos are at Codeberg [1] where my handle is "buhtz". I only
use GitHub (handle is "Codeberg-AsGithubAlternative-buhtz") because I'm
forced to.
I am using BIT since 2015. I will open new threads for more thoughts
and ideas about BiT.
About my background, skills and expertise in IT:
I haven't studied computer science or informatics at university. I
learned something called "Fachinformatiker" which is a 3-years school
vocational training to be something like a software developer. I worked
in that sector for one year only working on individual software using
C++. After then I became a nurse and after that a nursing scientist
currently working on my PhD.
- Today using Python for data science in my current employment as a
researcher
- Also used Python for an unknown amount of years for private projects
- Always tried to develop my Python skills including "professional"
topics like unit testing, clean code, CI, etc
- Touched C, C++, Java, RDBMS, ODBMS in the past
- Always interested in the topic of maintaining FOSS projects but
never did this myself.
Just a selection of my own (one-man) projects [1]:
- "Hyperorg" is a small tool converting org-files into simple HTML
files can be used without a web-server. "Org" (and "OrgRoam") is a
part of Emacs and could be (incomplete) described as a mixture from
note taking, personal wiki and Zettelkasten (and everything else you
need to "take over the world").
- "buhtzology" is my toolbox for code I reuse and prevent myself from
copy and paste my own code from project to project. Most of it has
data science background.
- "Feedybus" is a RSS/Atom Feedreader (aka Newsreader) and very
important to me. But the original (very old) repo is private because
the code currently doesn't reached my quality criteria. Current
status is "unusable" (even for me) because of heavy refactoring.
Looking forward for working with you.
Thanks for reading.
Christian Buhtz
[1] -- <https://codeberg.org/buhtz/hyperorg>
