-
Notifications
You must be signed in to change notification settings - Fork 45
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
Looking for new maintainers #277
Comments
Hi Paul, I use tablecloth regularly and really want this project to thrive. |
I still see tablecloth as a very viable choice for an alternative standard library of OCaml. Its API is much more consistent to me compared to Stdlib or Base, and much more modernistic with borrowed bits from Elm and maybe Rust. I would love to take up the work of moving tablecloth forward on OCaml platform. |
Thanks! Here's my current plan for moving forward:
|
Looks good to me. The only thing I would add is at some point in the future we should move these repositories to a tablecloth GitHub organisation. @pbiggar I suppose we can start picking up the work when we're splitting the repo? Or do you think there are things in |
Hmmm, tablecloth org is taken, but not by me. I wonder is it possible to contact the owner. |
Looking through the codebase, splitting the repo has some unanswered questions, such as what do we do about the website. So maybe let's work on switching to the new plan from #214 and go from there. |
I'm going to close this issue for now as it seems I'm still here. Let's move discussion into other issues, mostly #214. |
Since both we and Rescript moved away from OCaml, we aren't seeing the same value in maintaining tablecloth, and we certainly haven't kept up with the work required to keep it relevant and useful.
I'd love to see someone take over the maintainership who has the time and inclination to take it in the right direction (see #214 for what I think that is)
If no-one is interested, it might be best to deprecate tablecloth.
If you're interested, feel free to reach out by email or in the Darklang slack, or just comment below.
The text was updated successfully, but these errors were encountered: