-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request to add me as member to the repo so I can update the documentation #1119
Comments
@Codeberg-AsGithubAlternative-buhtz Do you have access to the Github config? |
Sorry, I have no access to the config or any other admin rights on @Germar 's repo. |
@Codeberg-AsGithubAlternative-buhtz Thanks for the info. It is IMHO really a shame that @Germar simply drops his project and is not even willing to hand it over to a new team. 😠 |
I have no idea why I was mentioned here 🤔 |
@LanceGundersen I mentioned you because you are listed as a member of BiT, see https://github.com/orgs/bit-team/people Do you have admin access to the BiT repos? |
We have to be careful before criticising @Germar. His facebook page has not been updated for a long time, perhaps some awful fate has befallen him. |
IMHO it is not fair to a team to just head off and let it stay for itself in the rain. And beside of this, if you search for @Germar in the internet you will find his portrait on a company website. So we gladly can interpret that he is doing well. |
I came here looking for support and vibrancy and I too am sad that it appears to be abandoned, especially when there are others who want to step up. Yes, I would be happy if this project found itself forked into a larger community so as to save it. The intention of the fork could be that it would be merged back if the original maintainer ever decided to come back to the project. |
I agree with @colinl . I just didn't want to describe it so direct. I hope @Germar is fine in these days. @caco3 This is not about fairness. And there is no "team". BIT was and is a one-man-show. I am a bit into it because I use it vey intensive. But myself I also not able to take over the project. Maintaining a project is not so easy as you might think. But "fair" is that you can fork everytime and improve it. It depends on your maintain abbility and your team which one of the repos will persist. |
I just want to inform that there is a newer Issue (#1232) discussing the status of the project and forming a new maintaining team. Since yesterday there is also mailing list about development and maintaining BIT. |
Hi @Germar, @dinoboy197, @LanceGundersen
I am using BiT since over 10 years, mainly in connection with my Synology Diskstation.
I also helped on the wiki page in https://github.com/bit-team/backintime/wiki/Hardware-Specific-Setups/_history
That page and several others are now quite outdated and really hard to maintain.
I would suggest to move it to https://backintime.readthedocs.io and update it. I am willing to help with that, but I would need to be a member of the repos for that.
The text was updated successfully, but these errors were encountered: