What is the future of this project?

[pvasek]

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:

1. Take over this project
2. Create a fork

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?

[jrolfs]

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 :)