gulp-community / meta Goto Github PK

The meta repository should clearly state the role of the organization in its README.md.

What are the reasons to move packages to gulp-community?

Suggestion

Create a community-maintained sass plugin. Ideally as @gulp-community/sass on NPM, so it's clear that this isn't just some random, one-time fork. I would be happy to write an implementation, which you could then look over before transferring.

Why

The more popular version, dlmanning/gulp-sass, doesn't look maintained. It hasn't been updated in over a year, and it breaks entirely on recent node versions (dlmanning/gulp-sass#797). It also depends on node-sass, so even if you want dart-sass, node-sass is still built and installed.

Hi since my gulp days some plugins have not gotten some love, so I would transfer them over here if you want:

• https://github.com/rejas/gulp-json-editor
• https://github.com/rejas/gulp-favicons

Also as a co maintainer I proposed to move this here too:

• ben-eb/gulp-svgmin#129

What do you think?

Hi, I want to know if gulp-terser-js (Github Page) can join your community ? Is a stable project since August 2019

For my test I use travis app:

Can we add this one ?

https://github.com/settings/connections/applications/88c5b97de2dbfc50f3ac

The maintainer of https://github.com/sirlantis/gulp-order would be willing to transfer it to this community, see gulp-community/gulp-order#30 (comment)

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.

I use Coveralls too for my repo :

https://github.com/settings/connections/applications/ad4c01c89848a307e228

I'd like to volunteer to maintain one or two of the community plugins, if necessary.

By "maintain", I mean...

1. Respond to issues
2. Review PRs
3. Foster a healthy community

However, I don't promise to update the code regularly, or even make patches. More than a triager, less than a developer.

Curious if you'd be open to moving gulp-header and footer to the community repo? I really haven't done much with either in a long while, but they're still relatively popular.