Move gulp-eslint-new to gulp-community

[fasttime]

I have a repo called gulp-eslint-new that I forked some time ago from the now unmaintained gulp-eslint in order to use ESLint 7 (now ESLint 8) with gulp. I've been putting a lot of work into this repo during the last two weeks or so to make it production-ready, but I can't promise to keep doing the same work in the future, so I thought that moving it here would help it gain more visibility and maybe find new contributors. Some users volunteered already but had no luck with gulp-eslint.

[phated]

@fasttime I appreciate you reaching out about this; however, saying "but I can't promise to keep doing the same work in the future" makes me skeptical of pulling this in. We're not trying to be a dumping ground for people that don't want to maintain packages they made. We've already had a few maintainers dump their projects, which is frustrating for the couple of us that actually work on things.

[fasttime]

@phated Maybe I wasn't very clear. I am willing to maintain this package in the future, but I won't be able to spend the same amount of work on it as I've done lately. I would prefer not to be the only maintainer.

[goldingdamien]

@phated
I am kind of in the same position as @fasttime .
I would be happy to take on some open source projects that I have used(some gulp related) and haven't been maintained recently, but not sure how much time I can commit.

I can understand being cautious, but there are lots of packages that end up not being maintained, and after a few years users generally just move on. This leads to multiple similar packages filling the void, fragmenting work for very little benefit.
It would be nice to see a proper discussion on this, and then maybe some guidelines, so both sides of this issue can act more accordingly.