-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the future of this project? #494
Comments
If I were using this project more actively right now, I'd probably volunteer to help with maintenance, but I worry I won't be able to prioritize it until I pick the work back up that leveraged this package. I'll try to look into this, but does Storybook still use this package actively? I was thinking @chromaui might be a good steward for this project and if they are indeed still using it in Storybook, they'd have a vested interest in keeping things going here. Also, I just want to say thank you again for your contribution to open source with this project @pvasek. Well done with the structure of this codebase :) |
Yeah, I'm also curious if someone at Chromatic (@chromaui) would be interested in maintaining it. While I'm actively using this library right now, I'll be transitioning off the project that uses it over the next couple months. I do know that they've changed the Storybook default in v8 to use |
Hi guys, as you could probably notice. I don't have time and interest to work on it anymore.
As @jrolfs correctly mentioned in PR #473, obviously this project is stalled out.
Is there anyone who is using this project and is interested in becoming a maintainer?
Options:
I guess option 1 would be easier for all who already using it. But there can be a tricky part with transferring npm package rights. Not technically but of course, I would have to trust this guy before doing so.
Option 2 is much easier in this case. I would just update the readme of this project pointing to the new one and that's it.
What are your opinions about it?
The text was updated successfully, but these errors were encountered: