Gluster does not depend much (unfortunately) on libfuse. At one time we
had the idea to rewrite our own implementation of the fuse bindings and
use the well tested and maintained libfuse. Possibly in combination with
libgfapi. This would reduce maintenance overhead quite a bit.
If someone still has an interest in persuading this, you might as well
want to support maintaining libfuse. I guess a small group of
maintainers is welcome (not expected to come all from Gluster). Get in
touch with Nikolaus and see what options there are.
> Date: Sat, 21 Mar 2020 10:49:55 +0000
> From: Nikolaus Rath <[hidden email]>
> To: [hidden email] > Subject: [fuse-devel] Call for new maintainer(s)
> Hi all,
> It's been about 5 years since I took over maintainership of libfuse from
> Miklos. Overall, I think this was a productive time: libfuse 3 was
> released, the build system was changed to Meson, a more extensive test
> suite added, the project moved from Sourceforge to Github, and I feel
> like the number of contributors has increased.
> However, since then my circumstances have changed. I am now a lot more
> occupied with work and family. My role in the project has become pretty
> much limited to triaging bugs, merging pull requests and doing the
> occasional release, and I don't expect to have time to do any actual
> development work anytime soon.
> In other words, I think libfuse would benefit from (one or more) new
> maintainers who can spend more time on it.
> If you think this role would be for you, please let me know. Ideally,
> you'd have some history of contribution to libfuse or other open-source
> projects and a lot of energy to drive things forward again.
> GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
> »Time flies like an arrow, fruit flies like a Banana.«