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

[pwolfert]

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 react-docgen, but people can still use react-docgen-typescript, and I imagine it's still going to be wildly popular for the foreseeable future. Thank you for all your work on this, @pvasek!

[pwolfert]

Not trying to put either of you on the spot but just trying to get eyes on it: @zol or @domyen, would your org be interested in this?

[zol]

Hey @pwolfert, I don't code very much anymore but I'll get with @shilman over here to see how maintaining this aligns with our plans for Storybook

[pwolfert]

I just noticed that at one point @shilman had published a fork of this on npm but that now the repo is archived. Any interested in reviving it and publishing some of the features and fixes in this repo from the past couple years, since you have the infrastructure to publish that package to npm?

[cgatian]

We use this for Storybook, and without a replacement on the horizon we will continue to support it!