search

Akryum / vue-virtual-scroller

⚡️ Blazing fast scrolling for any amount of data
https://vue-virtual-scroller-demo.netlify.app
9.69k stars 915 forks source link

Extra maintainer for vue-virtual-scroller? #806

Open JasonLandbridge opened 1 year ago

JasonLandbridge commented 1 year ago

Hi there,

This repo is amazing, but to little is done to keep it alive. @Akryum, I understand that you're busy and also working on your other repo's. Could I, or anyone else, get write access to resolve longstanding issues, update documentation and add more features?

I am hesitant to make pull requests since it seems they are either not getting through or taking a long time to get approved. For anyone else reading this, if you would like to volunteer as a maintainer then post a comment below. Also don't forget to like and subscribe!

Cheers!

yeminxuan commented 1 year ago

Yes, I do

Heunsig commented 1 year ago

I'll join

bmulholland commented 11 months ago

One way I've seen successful for picking up maintainer status is to fork it and start doing the work in that fork, merging PRs, etc. Either that eventually gets folded back into the original project, or the fork takes over. Either way, the longstanding issues get resolved.

amcjen commented 5 months ago

One way I've seen successful for picking up maintainer status is to fork it and start doing the work in that fork, merging PRs, etc. Either that eventually gets folded back into the original project, or the fork takes over. Either way, the longstanding issues get resolved.

I like to think this is how it should work, but this repo has 875 forks at the time of writing--I'm just not sure how to discover which one has the most activity/fixed issues/etc, short of reviewing each by hand.

Add to that, once you find a fork that has many of the fixes you want, you almost always need just one more item fixed from another fork, so you then merge it into your own fork. Now there are 876 forks.

Not trying to be negative--just that the discoverability of myriad forked versions rarely seems to rise above the "fixing it for my own needs so I can get back to it" situations a lot of us find ourselves in.

But absolutely hoping this repo gets the support it needs!