Maintenance #40
Replies: 4 comments 10 replies
-
As someone who occasionally uses packages from here like |
Beta Was this translation helpful? Give feedback.
-
I'm willing to take over maintenance of some of these packages (and move them to my account). I work on open-source full-time and want to make sure these packages are well maintained. I will not do major changes to the APIs. Just cleaning up the issue trackers, fixing bugs, and improving the readmes. I will obviously preserve the commit history and all credit for existing work. |
Beta Was this translation helpful? Give feedback.
-
Thank you @sindresorhus! I trust that you'll serve the open source community well! :) |
Beta Was this translation helpful? Give feedback.
-
I'd be happy to hand over packages to you, Sindre. Thoughts from @pirxpilot @matthewmueller @TooTallNate @juliangruber @yields? |
Beta Was this translation helpful? Give feedback.
-
Hi folks. Not sure who will see this notification, but I feel obligated to post.
About a decade ago, I was very active in the "component" community. Since then, I have moved on (you have too, probably). This said, we have many npm packages that are highly relied on (eg
debounce
, ~4M downloads a week). Do we intend on supporting these packages? If so, to what extent?I'd like to define a policy for future updates. I have no interest in introducing new features to anything, or even fixing bugs (if it's worked for 10+ years, it's probably fine). Can we all agree on something like this? Please discuss.
Cheers
Beta Was this translation helpful? Give feedback.
All reactions