Is this project still maintained?
Revive of #131
Last commit was about a year ago and @AGWA seems almost inactive for the last ~8+ years if I am not mistaken, so I am opening this issue to get an official statement from him on the future of this project.
At the time of writing, last release was 3.5 years ago.
Some people may claim that the project has reached its "maturity level", but still e.g. 27+ pull requests are piling up
On the previous iteration of this issue I made an offer to come on as a maintainer and later reiterated it. I linked instead of quoted those here because the votes and replies add some weight to the offer.
I'd still be up for being invited to help maintain this repository in place or better yet, starting an org where this could be migrated to so that I can help lead it as a more community effort. I've done this sort of thing before with other projects and have lots of trust credentials in the Linux FOSS ecosystem. I'd be happy to list some of those if trust is the hold up.
The encryption provided by git-crypt is of paramount importance to me, and there is currently no viable alternative. Certain issues have indeed impacted my usage and remain unresolved. I sincerely hope that its maintenance can continue.
example https://github.com/AGWA/git-crypt/issues/298
On the previous iteration of this issue I made an offer to come on as a maintainer and later reiterated it. I linked instead of quoted those here because the votes and replies add some weight to the offer.
I'd still be up for being invited to help maintain this repository in place or better yet, starting an org where this could be migrated to so that I can help lead it as a more community effort. I've done this sort of thing before with other projects and have lots of trust credentials in the Linux FOSS ecosystem. I'd be happy to list some of those if trust is the hold up.
@AGWA As a regular user of this project, I truly appreciate all the work that has been done so far—and I’m genuinely concerned about its future if active maintenance doesn’t resume.
Having reviewed some of the previous discussions, it seems there’s currently no clear plan to restore active maintenance.
I agree with @alerque suggestion that, at a minimum, bringing on 2–3 active maintainers to share the workload would be a practical step forward. As for migrating the project elsewhere, I remain open-minded but also respect the original author’s wishes and autonomy in that decision.
I sincerely hope this project can return to active maintenance—it remains a valuable resource for me and many other users.