No Longer Maintaining. Ideas welcome.

[jameskerr]

Hi Everyone,

I am no longer maintaining this repository. I have moved on from Brim Data and will no longer be giving this repo my development time.

What do you all thing we should do? Is there anyone out there continuing to develop this on a fork? Would anyone like to take over development? I'm not sure if it would be best to transfer the repo or to point to a new one. I'll have to also discuss these options with my former team at Brim.

Has anyone been in this situation before? Guidance welcome.

Best,
James

[markmoseley97]

I just forked it. I'm rusty on coding but I'll figure it out.

[haidar47x]

I hope someone with good knowledge of the codebase will take on the project. It's such a good library and it has served me so well for the past month.

[jledentu]

Hi @jameskerr. Thank you for caring about the future of this great library. I imagine the solution depends on whether Brim Data is willing to actively maintain the library or not. If not, it might be better to transfer the project to a dedicated organization (react-arborist)?

[alexsro]

Hi @jameskerr , is there any official statement on the status of Lib? Has a Brim Data maintainer or third party already been confirmed?

[fabiandecuveland]

What a pity, the only React tree view that fulfills our needs!

[mohsenomidi]

Is there any solution for maintaining or any other chance to have this library?

[TrevorBurnham]

I'd be happy to help maintain this package. It seems to still be best-in-class, despite a year of stagnation.