if you're going through all the trouble of forking you want to build a community around your fork, so you're not the only one maintaining it.

C'mon, it's forking a whitelist.

no, i was around in the elm community at the time, and what people wanted to fork for was a better way to support native js code in their own projects. there was a bit more to it than just adding filenames to a whitelist.

Once the maintainer has ignored all community feedback on said whitelist and then threatened said members of community for considering removing the whitelist, why in the world would you assume it'll remain "just a whitelist"?