> >> I'm maintaining our DDN internal version anyway - I think I can help to > >> maintain libfuse / take it over. > >> > >> Btw, I also think that kernel fuse needs a maintenance team - I think > >> currently patches are getting forgotten about - I'm planning to set up > >> my own fuse-bernd-next branch with patches, which I think should be > >> considered - I just didn't get to that yet. > >> > >> > >> Thanks, > >> Bernd > > > > +1 for Bernd's maintenance *team* idea. But perhaps extended to libfuse > > as well? There are a number of us who are familiar with the code and at > > least semi-active in the space. Help spread the load. > > > > I could help out at least on the libfuse side. > > You are absolutely right, a team is always better. Might also be a good opportunity to start the linux-fuse mailing list on kernel.org. I find the disjoint fuse-devel and linux-fsdevel mailing lists a bit counter productive for new fuse feature development, which afaik, are mostly driven by linux-fuse driver developers these days. Thanks, Amir.
