search

svg / svgo

⚙️ Node.js tool for optimizing SVG files
https://svgo.dev/
MIT License
20.83k stars 1.38k forks source link

Call for new maintainer(s) #1320

Open deepsweet opened 3 years ago

deepsweet commented 3 years ago

Hi.

My name is Kir, I'm the original author (2012-2016) of SVGO. Current maintainer @GreLI seems to be quite away from GitHub recently and I think it's time to call for new people interested in the project.

With 10M of weekly downloads from NPM I'm not exactly sure how to choose someone and grant access, it sounds like a great responsibility. I'd probably start with reviewing some PRs from a candidate and then maybe a video call. Just want to make sure it's in good hands.

Anyone?

paulocoghi commented 3 years ago

@strarsis is a strong candidate :)

strarsis commented 3 years ago

Yes, I would like to improve svgo as I use it mysql myself quite a lot.

TrySound commented 3 years ago

Hi @deepsweet! I would like to help with refreshing the package and fixing some issues. I already submitted a few pull requests. https://github.com/svg/svgo/pull/1293 https://github.com/svg/svgo/pull/1292 https://github.com/svg/svgo/pull/1291 https://github.com/svg/svgo/pull/1290

paulocoghi commented 3 years ago

@strarsis I just don't understand the mysql term on your phrase. :smile: I'm a little confused xD

sk- commented 3 years ago

In the short term I think something along the following lines should be done, so that users know that the project is indeed not dead and is going to be actively maintained.

For the medium term:

Longer term:

lazee commented 3 years ago

@deepsweet Thank you for this initiative and for your magnificent work with svgo.

I understand your need to find a trustworthy and good maintainer for this project. Whether that is @strarsis, @TrySound, @sk- (or anybody else) is yet to be seen. Personally, I don't have the time, but I will help with PRs where I can as soon as I know there is a fair chance that it will end up in the codebase.

I agree with all that @sk wrote. I would like to add that it should be kept backward compatible (as there are so many packages that depends on it) and...it would be so cool if the codebase could be split up so that we, somewhere down the road can have Deno support as well ;)

TrySound commented 3 years ago

Hi guys. I'm maintainer now. Feel free to ping me in issues or pull requests.

strarsis commented 3 years ago

@TrySound: Merging these PRs would be nice:

yisibl commented 3 years ago

TrySound is an excellent maintainer!

yoriiis commented 1 year ago

I'm not sure but the topic still seems relevant to me.

The project seems a bit slowed down, and the number of issues is quite high, ~230 currently. Moreover, there are regressions since the last release and no response on Discord and GitHub.

The project is great, really! But, as a user and contributor, I think it's important to be transparent. Is there a need for support on the project?

The subject is sensitive and is in no way negative, I am also a project maintainer and I can understand that we also have other obligations.

deepsweet commented 1 year ago

Hi @yoriiis

Here is my comment regarding this from another thread https://github.com/svg/svgo/issues/1128#issuecomment-1405767522:

I'm the original author as it says in the `package.json`. I have all the possible access both here and on NPM, but not the time and necessary context to continue working on the project. For many years. At the same time I can't just blindly merge PRs to the project with 15M NPM downloads per week, so I've tried to look for maintainers over the years. It's way more complicated than it seems to be, starting from the observation that there are no many candidates. In fact, there are none. One thing is to merge old and stalled for months PRs, and another is to develop it all further and push forward. The only realistic way to dramatically change this situation is to contribute and be ready to become a new maintainer. Talk to me.

Re-opening and pinning this issue again.

paulocoghi commented 1 year ago

Considering the usage stats, it's not unrealistic to estimate that SVGO is used on many commercial cases and, thus, I propose the creation of an easy path to receive recurrent sponsorship/donations.

If just a fraction of the commercial users recurrently sponsor SVGO, it may be enough to pay for fixed contributors, at least one.

Just my 2c.

(Edit) Possible sources of funding/sponsorship and/or platforms to help:

paulocoghi commented 1 year ago

If only 3% of the stargazers contribute with an average of $7/mo (some $5, some $10), this would generate $4k+ a month. Only 3%.

GreLI commented 1 year ago

It never works that way, unfortunately. More realistic is getting some big sponsorship from large companies.

Also, project like this requires at least a couple of full-time maintainers to be carried in a good pace. But I don't think, that something like that can happen. Spare time of a few volunteers is not enough.

SethFalco commented 12 months ago

As a regular user myself, I would be happy to help maintain svgo if you'd have me. I have availability to at least triage/resolve issues, fix reported bugs, improve documentation etc.

I've opened issues before, and have recently opened some pull requests. I understand it may not be enough yet, but just wanted to have my name down as interested already.

deepsweet commented 12 months ago

@SethFalco hi! You should be able to manage issues and PRs now. Please let me know when you're ready to publish a new version to NPM, I'll provide access token.

SethFalco commented 12 months ago

@deepsweet Hey! Sorry to pester, I just want to verify your intent here!

let me know when you're ready to publish a new version to NPM

You've granted triage access, so I can manage issues and PRs. But only actions like approving or requesting changes, or cleaning up invalid issues. It does not allow running workflows on pull requests or write access, which would be normal to justify prompting for a new version.

Can you clarify if you intended to grant triage access or write access?

deepsweet commented 12 months ago

@SethFalco fixed, changed access to write.

TrySound commented 12 months ago

You can communicate with us in discord

SethFalco commented 12 months ago

You can communicate with us in discord

I actually stray away of Discord and deleted my account some time ago! I should've clarified that in my initial post, as I did notice the Discord link in the README. 😅

Let me know if that's a problem. Meanwhile, I'm always available on Matrix, Mastodon, email, and LinkedIn. ^-^' Would also be more than happy to participate if it's ever bridged over!

danielbayley commented 11 months ago

@deepsweet I’m already way overextend currently 😅 But once the dust settles, I have much to contribute to this often used project…