ku1ik/bitpocket

is bitpocket still maintained ?

jpcaruana opened this issue · 5 comments

Hi,
is bitpocket still maintained ? If not, is there any official fork ?
It's a nice tool

thanks

I'm one of the maintainers of bitpocket (the other one is sickill, who is the original author).

I would say that bitpocket is still maintained, even though the maintenance is not very active. As far as I see it, maintenance of bitpocket is mostly limited to fixing data-loss bugs and merging pull requests. It is also, of course, limited by the time of the maintainers.

That said, I do know that there are several open pull requests that have not been merged. From my perspective, the most important issue is avoiding data loss at all costs, so I'll want to take a pretty good look at any pull requests before including them. Each comment from current users does increase the likelihood that I take the time to merge them, though :-)

I don't know of an official fork, and if there is someone out there who'd be willing to put in the time to be a more active maintainer than sickill and I are, I'm pretty sure sickill would be happy to grant them commit access to this repository instead of doing it as a fork. Given some proof of intent, of course. Not that I would speak for him, but he was very open to giving me access after I made some contributions.

I can just repeat every single word that @torfason wrote :)

Also, bitpocket is quite complete feature-wise in my opinion. Of course, there are many things that are not included and would be beneficial for many users but I'm afraid that bitpocket reached a point where it's not possible to add any new major feature without dropping rsync as the core dependency and reimplementing rsync's functionality from scratch. It started as a thin, smart wrapper around rsync and it's highly tied to it.

Having said that I will repeat after @torfason that small improvements and bugfixes are always welcome. My time is limited recently so it may look like it's a bit unmaintained, true. But I really appreciate that @torfason engaged with the project, making great contribution to it.

ok thanks for your answers.

ku1ik commented

We have several open issues and PRs that need looking into. I don't really have time for this project anymore. What about you @torfason? Should we look for new maintainers?

Unfortunately I'm in the same situation, these days I do not have time for any updates. Realistically, I won't manage any pull requests in the near or medium future. I'd second getting new maintainers if any are to be found ...

On the plus side, it's a very neat and simple to understand script (apart from a few sections where it needs to work around the quirks of the underlying commands), so a new maintainer could get up and running quickly.