Community maintenance

Dear fsspec community!

I am writing to you as you have associated yourself with fsspec or one of the implementations. As the code base and number of backends grows, there is ever more chance of friction between maintaining consistency and adding more features; async and batch operations have been a good example of this.

Furthermore, it is a bad idea to have myself as the only maintainer and releaser of the packages, should critical bugs arise when I am not available.

Please let me and this group know whether you have any interest in being more involved in the day to day maintenance of filesystems, or if you have opinions on how to go about providing a continuing smooth experience to users. Also, please add any other interested parties I have forgot to include!

Community

• @rjzamora to represent Dask IO
• @jorisvandenbossche to represent (py)arrow
• someone from zarr, xarray, pandas?

Maintainers

• @hayesgb of aldfs
• @MarineChap of dropboxfs
• @rabernat of gdrivefs

Recent contributors:

• @ahirner
• @raybellwaves
• @baxen
• @JacobHayes
• @namanjain
• @mariusvniekerk
• @gerritholl
• @ajkerrigan
• @hadim (+ other pathlib interested people?)

No files, tests, or entry points are named; start by reading the issue discussion and the current maintainer and contributor context. The issue has no concrete implementation task or definition of done, so a contributor would first need an agreed maintenance plan.