Skip to content
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

Fork this project #212

Open
tlivings opened this issue Dec 6, 2021 · 3 comments
Open

Fork this project #212

tlivings opened this issue Dec 6, 2021 · 3 comments

Comments

@tlivings
Copy link
Contributor

tlivings commented Dec 6, 2021

I think it makes sense to potentially fork this project to maintainers willing to continue work on it and redirect users in the readme to the new maintained project.

Afaik the Kraken team doesn't actively maintain this project and I haven't had time in a while to keep up with it.

Thoughts @dcharbonnier ?

@dcharbonnier
Copy link
Contributor

I agree, if this can't stay in the same namespace with more people that have access to issues, and merge requests.
But I won't maintain it alone, no point if nobody check the PR at least.

@dcharbonnier
Copy link
Contributor

ping @tpburch @alferpal @sommestad

@alferpal
Copy link
Contributor

alferpal commented Dec 6, 2021

Thanks for the ping.

In the end we went with a different approach to what we needed and didn't ended up using this.

Kind of built something a bit similar on top of ajv, more tailored to what we needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants