Final Notice: Maintainers Wanted · Issue #413 · fsnotify/fsnotify · GitHub

This is a final notice. fsnotify is a fork of @howeyc's library that I made many years ago, but I am no longer willing to maintain. To be honest, I have done very little to maintain the project in recent years, so I believe that letting go is the best thing I can do.

Either new maintainers will take over the project by February 28, 2022, or this project will be archived.

If the project is archived, the code will still be available for use, but no further changes or issues will be possible. At that point it will be up to the open source community at large to decide whether or not to fork the project.

Either way, I will be officially leaving the project.

Things to know about the project

• According to pkg.go.dev, fsnotify is in use by over 4000 open source packages. Any changes must be carefully considered and semantic versioning must be strictly followed.
• fsnotify is a low-level library, and many of the issues reported stem from issues with the underlying event notification systems. Whether or not those issues can be solved with code or not, I do not know. It may be that providing better documentation will stave off the same issues being opened repeatedly.
• fsnotify is a cross-platform library, which means that any API changes must take into account all platforms. GitHub Actions does not cover every platform that fsnotify supports (e.g. BSD), so manual testing on multiple platforms may be necessary.
• Not every maintainer needs to maintain support for every platform, but it's important that every maintainer is ensuring cross-platform compatibility.
• There are quite a few open issues, unreviewed pull requests, and the existing code base is rough in spots (especially Windows support).

How to become a maintainer

I will not be handing out administrative access to just anyone.

There are a few ways to show I can trust you to become a maintainer:

• If you have previously contributed to fsnotify
• If you are someone I know personally
• Start helping to triage issues (which are often duplicates) and open pull requests, then come back and ask

Please comment below. Indicate your name, number of years experience maintaining other open source projects, your primary platform, platforms willing to support, number of hours per week/month you're willing to contribute.

NOTE: this issue replaces a 5-year old call for maintainers #183