Decide which ESPAsyncWebServer fork should be canonical? #34
Description
[edited based on discussions] The situation with ESPAsyncWebServer is a mess:
- the original repo appears to be unmaintained, and is extremely buggy
- this repo is quite popular and contains many fixes (but not all?) but is more oriented to esphome's needs?
- the Arduino registry's entry for ESPAsyncWebServer points to @lacamera's fork of this repository, which is just this repo plus
library.properties - the most visible platformio registry entry points to me-no-dev's original repo, and people are actively steered there
- other notable forks are @mathieucarbou's fork and the yubox-node-org fork
Ideally we'd designate one repo and merge the important fixes and improvements there, and any remaining forks would work off that if people need to add project-specific tweaks? And we could see about changing registry entries to point to that fork, or at least steer people there?
The most likely candidates seem like this one and @mathieucarbou's fork; Mathieu seems to be actively merging in fixes from elsewhere and seems to be willing to take up the mantle, so that's one promising option?
But, I'm sure people have Opinions...